[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ke, Liping" <liping.ke@xxxxxxxxx>
  • Date: Mon, 26 May 2008 16:20:54 +0800
  • Delivery-date: Mon, 26 May 2008 01:21:26 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aci6Rwan30LCwMVNRjCgsXSrb2rzYwAOb9TQAAFWQHAAAIxGwAAAHx6dAACz6YAAAGA27AAfNwegAG4iWxMAi2IGYAAEQNRaAADEEWAAADQJyAAA1HIQ
  • Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent

Hi, Keir
It works fine, I test vcpu=1 or 2 on FC6_32p and FC8_32e
So no other problems I could see now -:). 
Thanks a lot!!
Regards,
Criping

 

-----Original Message-----
From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
Sent: 2008?5?26? 15:49
To: Ke, Liping; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent

Hopefully it is fixed by c/s 17730. I did not see this with a Fedora kernel,
perhaps because I tested a single-processor guest and perhaps that VCPU was
dropped into real mode before triggering S3. I'm not sure. Anyhow S3
definitely didn't work properly so I suspect there are still one or two bugs
which some wider testing coverage would pick out.

 -- Keir

On 26/5/08 08:45, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:

> Hi, Keir
> 
> Yes, actually by case 4, I found the problem. Because vtd-assigned guest
> will first check whether the pci device is available first.
> I did not verify it on 32bit guest yet.
> 
> Regards,
> Criping
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: 2008?5?26? 15:21
> To: Ke, Liping; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent
> 
> On 26/5/08 07:11, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:
> 
>> 4) fc8_32e, vtd nic assigned. It works fine. Yet found still find below
>> problem
>>     domain_destroy is not completed, so vtd-resources are not freed totally.
>> So when
>>     you destroy this domain and recreate the domain process will fail.
>> 
>> Also verified with even have update_paging_modes, cr3 missing
>> domain_page error problem still exists. I remember I tracked the problem
>> before,
>> When update_page_mode, if we changed cr3, it will put_page(old cr3 page) and
>> Get_page(new cr3 page), so it will keep balance. But for this s3 case,
>> since when sleep down it is in protected mode, when back it begins from real
>> mode, so 
>> the cr3 used in protected mode is never put?
> 
> Do you see this only in case 4 (64-bit guest with VT-d assignment)?
> 
>  -- Keir
> 
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.