 Home |
Products |
Support |
Community |
News |
xen-ia64-devel
Re: [Xen-ia64-devel] where's phys_to_machine?
| To: | "Tristan Gingold" <tgingold@xxxxxxx> |
|---|---|
| Subject: | Re: [Xen-ia64-devel] where's phys_to_machine? |
| From: | "David Brown" <dmlb2000@xxxxxxxxx> |
| Date: | Wed, 14 Feb 2007 21:44:21 -0800 |
| Cc: | Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Wed, 14 Feb 2007 21:43:29 -0800 |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=il2L29XdQ/QQgg35I/DhOxk7azK2pSoOFRXwVTkfkS31Bqcu7rT8+fPIxTb87J9MI9uXdB7V8jiEwbflKyk8q3zbpYl09mbXbtoK8waoIM1KCWgalRETfYCzPJ+vF8+JgITCeRAl/02PKr70uzeq3VUHhGU5CIhNK3oKoH/MjQ8= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20070215052434.GA2503@saphi> |
| 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> |
| References: | <9c21eeae0702141000i4dce681we0dc4590c7ca553c@xxxxxxxxxxxxxx> <20070215021521.GB19041%yamahata@xxxxxxxxxxxxx> <20070215052434.GA2503@saphi> |
| Sender: | xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 2/14/07, Tristan Gingold <tgingold@xxxxxxx> wrote: On Thu, Feb 15, 2007 at 11:15:21AM +0900, Isaku Yamahata wrote: [...] > Probably the ia64 counter part is phys_to_machine_for_dma(). > It convers pseudo physical address to machine address. > In general, device drivers shouldn't call phys_to_machine() directly. > For dma, device drivers should use dma api. > For IO area access, device drivers should use ioremap()/iounmap(). > > This is only the theory and presumably you already know it. > The device which you are playing with might have strange aspects, > I guess. IIRC the Quadrics cards are designed to be programmed directly by the user. They therefore have an MMU, which has to be updated. Not a really simple driver ! Correct there's lots of fun stuff you can do with the quadrics drivers in a working cluster. They aren't a simple driver by any stretch of the imagination, I just wanted to make sure I translated the code correctly to ia64. Thanks. - David Brown _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-ia64-devel] where's phys_to_machine?, Tristan Gingold |
|---|---|
| Next by Date: | [Xen-ia64-devel] [PATCH][Bug 900] Fix xc_vcpu_{set/get}affinity, Masaki Kanno |
| Previous by Thread: | Re: [Xen-ia64-devel] where's phys_to_machine?, Tristan Gingold |
| Next by Thread: | [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13904, Zhang, Jingke |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
