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-ia64-devel

Re: [Xen-ia64-devel] [RFC] Extended I/O port space support

To: Jes Sorensen <jes@xxxxxxx>
Subject: Re: [Xen-ia64-devel] [RFC] Extended I/O port space support
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Wed, 13 Jun 2007 06:31:52 -0600
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 13 Jun 2007 05:29:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <yq07iq814un.fsf@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: HP OSLO R&D
References: <1181255641.6634.22.camel@lappy> <20070608051116.GA2498@saphi> <yq07iq814un.fsf@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2007-06-13 at 07:17 -0400, Jes Sorensen wrote:
> >>>>> "Tristan" == Tristan Gingold <tgingold@xxxxxxx> writes:
> Tristan> This is certainly the right way to do it, but you also have
> Tristan> to specify to the driver domain the io space base (although
> Tristan> it can be remapped).
> 
> First thing that sprung to mind when I read Alex's posting was: does
> anybody actually use IO-ports on ia64 anymore? I thought we managed to
> effectively eliminate them?

   Quite a lot of PCI cards still have I/O port space bars, but
hopefully any "high speed" devices use their MMIO bars exclusively.
This is mainly needed for correctness.  Before this patch, a driver
domain would spew a huge number of errors about trying to map MMIO pages
that Xen wasn't aware.  Once it finally did boot, most drivers seem to
avoid using I/O ports, so the devices work ok.  Then Xen would crash if
I shutdown the domain.  All that is fixed by properly registering and
setting up the I/O port ranges.  And if there is a driver that still
pokes I/O port space bars, at least it will work now.

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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