All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>,
	ian.campbell@citrix.com, andres@lagarcavilla.org,
	ian.jackson@citrix.com, Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: memop struct packing, 32/64 bits
Date: Mon, 23 Jan 2012 10:02:01 -0500	[thread overview]
Message-ID: <20120123150201.GA11441@phenom.dumpdata.com> (raw)
In-Reply-To: <4F1D355D020000780006E4E9@nat28.tlf.novell.com>

On Mon, Jan 23, 2012 at 09:24:29AM +0000, Jan Beulich wrote:
> >>> On 22.01.12 at 21:37, Konrad Rzeszutek Wilk <konrad@darnok.org> wrote:
> > So for the "Fun" of it I tried to see if the 'struct
> > xen_processor_performance' has some 32/64-bit issues and was surprised
> > to find they do. What I am more surprised to find is that nobody seems
> > to have had any troubles with this as it seems to have been there since
> > it was initially implemented. The major issue would have been with the
> > 'shared_type', 'domain_info' and the pointer to the 'states' being at
> > different offsets (So when running a 32-bit dom0 with a 64-bit
> > hypervisor).
> 
> Are you having an actual problem with the layout differences, or
> did you just observe them? As Keir said, this is being dealt with
> inside the hypervisor - the (Dom0) kernel doesn't need to care at
> all (which was the primary requirement when the 32-on-64
> support got added).

I just observed them when I was trying to use memcpy on the Linux<->Xen
structs and saw some padding issues. The further I looked the more
I saw of it and was wondering why nobody had tripped over it.

But the compat layer that Keir pointed to me does fix the 32/64 bit
issue I observed - so wheew, no bugs!

Thanks!
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2012-01-23 15:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 20:30 memop struct packing, 32/64 bits Andres Lagar-Cavilla
2012-01-19 20:49 ` Keir Fraser
2012-01-19 20:57   ` Andres Lagar-Cavilla
2012-01-19 21:11     ` Ian Campbell
2012-01-19 21:21       ` Andres Lagar-Cavilla
2012-01-19 21:23       ` Andres Lagar-Cavilla
2012-01-19 21:56         ` Keir Fraser
2012-01-19 22:00           ` Keir Fraser
2012-01-19 22:04             ` Keir Fraser
2012-01-19 22:05             ` Andres Lagar-Cavilla
2012-01-22 20:37   ` Konrad Rzeszutek Wilk
2012-01-22 20:43     ` Keir Fraser
2012-01-23  9:24     ` Jan Beulich
2012-01-23 15:02       ` Konrad Rzeszutek Wilk [this message]
2012-01-19 20:49 ` Konrad Rzeszutek Wilk
2012-01-19 21:07   ` Keir Fraser
2012-01-19 21:12     ` Ian Campbell
2012-01-19 21:56       ` Keir Fraser
2012-01-20 10:12         ` Jan Beulich
2012-01-20 10:32           ` Keir Fraser

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=20120123150201.GA11441@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andres@lagarcavilla.org \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=keir@xen.org \
    --cc=konrad@darnok.org \
    --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.