 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [Xen-
| To: | Isaku Yamahata <yamahata@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [Xen-devel] [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification) |
| From: | Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
| Date: | Wed, 03 Dec 2008 10:15:33 +0000 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Wed, 03 Dec 2008 02:16:05 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20081203101353.GJ15798%yamahata@xxxxxxxxxxxxx> |
| 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> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| Thread-index: | AclVMBN1MFZ4iXd39EWrwxfzXeczug== |
| Thread-topic: | [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [Xen-devel] [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification) |
| User-agent: | Microsoft-Entourage/12.14.0.081024 |
On 03/12/2008 10:13, "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx> wrote: >> If you are fully virtualised then gmfn should mean gpfn, and >> arbitrary_virt_to_machine() is correct, isn't it? I can't see a situation >> where arbitrary_virt_to_machine() wouldn't correctly give you a gmfn (after >> all, it gets you a machine address in guest context, as its name describes >> :-). > > Oh, you are quite right. > Do you agree to rename PHYSDEVOP_pirq_eoi_mfn to PHYSDEVOP_pirq_eoi_gmfn? Yes, and I'll fix up your patches myself to use a_v_t_m() always. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
