From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification)
Date: Wed, 03 Dec 2008 10:15:33 +0000 [thread overview]
Message-ID: <C55C0CC5.1FCBF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20081203101353.GJ15798%yamahata@valinux.co.jp>
On 03/12/2008 10:13, "Isaku Yamahata" <yamahata@valinux.co.jp> 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
next prev parent reply other threads:[~2008-12-03 10:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 9:59 [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification Jan Beulich
2008-12-03 2:07 ` [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification) Isaku Yamahata
2008-12-03 7:58 ` Jan Beulich
2008-12-03 8:44 ` Isaku Yamahata
2008-12-03 8:58 ` Jan Beulich
2008-12-03 9:20 ` Isaku Yamahata
2008-12-03 9:31 ` Jan Beulich
2008-12-03 9:59 ` Isaku Yamahata
2008-12-03 10:08 ` Keir Fraser
2008-12-03 10:13 ` Isaku Yamahata
2008-12-03 10:15 ` Keir Fraser [this message]
2008-12-03 10:23 ` Isaku Yamahata
-- strict thread matches above, loose matches on Subject: below --
2008-12-08 13:36 Jan Beulich
2008-12-09 3:40 ` Isaku Yamahata
2008-12-09 10:04 ` Jan Beulich
2008-12-09 10:43 ` Isaku Yamahata
2008-12-09 10:54 ` Jan Beulich
2008-12-09 11:06 ` Keir Fraser
2008-12-10 4:08 ` Isaku Yamahata
2008-12-10 4:16 ` Isaku Yamahata
2008-12-10 4:09 ` Isaku Yamahata
2008-12-10 7:59 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C55C0CC5.1FCBF%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.