WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] HVM with old kernel(rh5.1) assigned device resume failur

To: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] HVM with old kernel(rh5.1) assigned device resume failure because of restore sequence
From: "Ke, Liping" <liping.ke@xxxxxxxxx>
Date: Fri, 17 Apr 2009 15:06:55 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 17 Apr 2009 00:08:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090417155702.93F1.27C06F64@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E2263E4A5B2284449EEBD0AAB751098401CFD2667E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090417155702.93F1.27C06F64@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acm/KfuIhaF3o3YBQwSJ86zq+9juLQAAOkAg
Thread-topic: [Xen-devel] HVM with old kernel(rh5.1) assigned device resume failure because of restore sequence
Hi, Shimada
OK, thanks a lot. It would be nice.
So you will send out the small fix or you want us to make the patch?
Regards,
Criping


Yuji Shimada wrote:
> On Fri, 17 Apr 2009 10:32:31 +0800
> "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:
> 
>> Older kernel(before 2.6.18 in rh5.1) cmd register is restored before
>> Bar register, 
>> it will cause qemu passthrough pt_mapping_bars failure.
>> (In qemu, pt_bar_mappings is done in pt_cmd_reg_write.
>> pt_bar_reg_write is not performed 
>> yet, then pt_bar_mappings can't map the correct address)
>> Latest kernel (after 2.6.2X) has no such problem. (When do
>> pt_bar_mapping in pt_cmd_reg_write, pt_bar_reg_write is already
>> done). 
>> 
>> I pasted corrected Qemu(2.6.29) log (line 660) and uncorrected
>> Qemu(rh5.1) Log (Line 554) 
>> and add [ criping XXX] comments for your reference.
>> For supporting old kernel, could we consider to change the
>> pt_bar_mappings sequence in Qemu? We'd like to have your opinions
>> first. 
> 
> The following modification is required.
> 
>   When pt_bar_reg_write is called, it should call pt_bar_mapping if
>   memory space bit or IO space bit in command register is '1'.
> 
> As a result IO/memory resource is mapped at the correct address.
> 
> Thanks,


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