From: Keir Fraser <keir@xensource.com>
To: Stefan Berger <stefanb@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] [ACM] Comilation fix for 32 bit
Date: Thu, 26 Apr 2007 11:55:06 +0100 [thread overview]
Message-ID: <C256439A.DF63%keir@xensource.com> (raw)
In-Reply-To: <OFE6C07EAC.B5A0146F-ON852572C9.003ADC9B-852572C9.003B6C91@us.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]
On 26/4/07 11:49, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>> > You're better off keeping the GUEST_HANDLE_64() and getting rid of the
>> > compat acm stuff. As far as I can see, all your interfaces are *currently*
>> > 32/64-bit invariant. So the compat stuff can safely be removed and then you
>> > don't need to continually keep it sync.
>
> I was going to ask you about this. I am writing on a patch that puts all the
> ACM hypercall structures into a union. I am wondering what the compat stuff is
> for (xen/common/compat) and what the criterion is for needing this compat
> code.
>
If you have structures that differ in layout in 32-bit mode vs. 64-bit mode
then you need a compat shim when running 32-bit dom0 on 64-bit Xen (which we
support doing nowadays). Currently you have no such issues that I¹m aware
of. You should be able to delete the compat stuff that is there currently
with no problems.
Is the build failure in Xen itself or in tools? I¹m sure it¹s easily fixed
without needing to throw away the GUEST_HANDLE_64() usage.
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 1647 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-04-26 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 3:36 [PATCH] [ACM] Comilation fix for 32 bit Stefan Berger
2007-04-26 6:50 ` Keir Fraser
2007-04-26 10:49 ` Stefan Berger
2007-04-26 10:55 ` Keir Fraser [this message]
2007-04-26 10:59 ` Stefan Berger
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=C256439A.DF63%keir@xensource.com \
--to=keir@xensource.com \
--cc=stefanb@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.