xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: One question to compat model
Date: Thu, 13 May 2010 11:04:38 +0100	[thread overview]
Message-ID: <C8118D46.14254%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731E5F281D@shsmsx501.ccr.corp.intel.com>

On 13/05/2010 11:00, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:

>> I was probably being overzealous. There's no good reason not to use
>> GUEST_HANDLE_64 and uint64_aligned_t outside of tools interfaces.
> 
> Althoug not related with my current patch, but curiosly, will it avoid the
> compat model issue if we use XEN_GUEST_HANDLE_64 for hypercall, especially if
> not performance critical, like struct xen_mc_fetch? (Maybe we still need
> consider the #pragma pack optoin for the struction?)

Oh yes, it would be a *very* good idea to use these macros to avoid the need
for compat shim code at all.

 -- Keir

      reply	other threads:[~2010-05-13 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12  7:38 One question to compat model Jiang, Yunhong
2010-05-12  8:00 ` Jan Beulich
2010-05-12  8:15   ` Jiang, Yunhong
2010-05-12  8:31     ` Jan Beulich
2010-05-12  8:50       ` Jiang, Yunhong
2010-05-12  9:11         ` Jan Beulich
2010-05-12  9:14           ` Jiang, Yunhong
2010-05-12  9:13         ` Keir Fraser
2010-05-13  8:41           ` Jiang, Yunhong
2010-05-13  8:48             ` Keir Fraser
2010-05-13 10:00               ` Jiang, Yunhong
2010-05-13 10:04                 ` Keir Fraser [this message]

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=C8118D46.14254%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).