From: "Jan Beulich" <jbeulich@novell.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] fix c/s 18938
Date: Fri, 27 Mar 2009 17:08:00 +0000 [thread overview]
Message-ID: <49CD1600.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200903271749.15350.Christoph.Egger@amd.com>
>>> Christoph Egger <Christoph.Egger@amd.com> 27.03.09 17:49 >>>
>On Friday 27 March 2009 17:34:07 Jan Beulich wrote:
>> - * Currently Intel extended MSR (32/64) including all gp registers
>> - * and E(R)DI, E(R)BP, E(R)SP, E(R)FLAGS, E(R)IP, E(R)MISC, only 10
>> - * of them might be useful. So expend this array to 10.
>> - */
>> - struct mcinfo_msr mc_msr[10];
>> + * Currently Intel extended MSR (32/64) include all gp registers
>> + * and E(R)FLAGS, E(R)IP, E(R)MISC, up to 11/19 of them might be
>> + * useful at present. So expand this array to 16/32 to leave room.
>> + */
>> + struct mcinfo_msr mc_msr[sizeof(void *) * 4];
>
>Please make this a fixed sized array. There are users like Oracle who run
>a 32bit PAE Dom0 on a 64bit Xen ...
And you expect a 32-bit kernel to be able to make sense of the MSRs
corresponding to 64-bit-only registers?
But you remind me that I failed to handle the difference in size of that
array for 32-on-64 - I really need to check why the structure layout
checking logic didn't catch the difference in size. Oh, right, sizeof(void *)
needs special treatment (and I really don#t want to sue sizeof(long)
here due to the implied dependency on the OS ABI).
Jan
next prev parent reply other threads:[~2009-03-27 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 16:34 [PATCH] fix c/s 18938 Jan Beulich
2009-03-27 16:49 ` Christoph Egger
2009-03-27 17:08 ` Jan Beulich [this message]
2009-03-27 17:21 ` Christoph Egger
2009-03-30 7:14 ` Jan Beulich
2009-03-27 17:22 ` Frank van der Linden
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=49CD1600.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Christoph.Egger@amd.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.