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

RE: [Xen-ia64-devel][PATCH] a small fix in mm.c


  • To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Thu, 25 Sep 2008 10:14:02 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 24 Sep 2008 19:14:26 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: Ackes6YIkN/d9g6jS4WRUX+CL/zX0gAAB7ow
  • Thread-topic: [Xen-ia64-devel][PATCH] a small fix in mm.c

Isaku Yamahata wrote:
> On Wed, Sep 24, 2008 at 02:50:54PM +0800, Xu, Anthony wrote:
>> A small fix in mm.c
>>
>> Signed-off-by, Anthony xu < anthony.xu@xxxxxxxxx >
>
> Hi Anthony.
> This patch looks correct.
>
> Have you tested this patch with pciback/pcifront?
NO , I didn't.

I think only driver domain will use this code path, when a device is assigned 
to driver domain, its Ioport will also be assign to driver domain.
I don't think pciback/pcifront will use the code path.

Anthony


> They have been supported and the code path surely is used
> with the driver. So I'm wondering why this hadn't
> been detected so far.
>
> thanks,

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


 


Rackspace

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