From: Tim Deegan <tim@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH 1/15]: PVH xen: turn gdb_frames/gdt_ents into union
Date: Thu, 24 Jan 2013 16:18:08 +0000 [thread overview]
Message-ID: <20130124161808.GI20551@ocelot.phlegethon.org> (raw)
In-Reply-To: <5101674E02000078000B93F8@nat28.tlf.novell.com>
At 15:54 +0000 on 24 Jan (1359042878), Jan Beulich wrote:
> >>> On 24.01.13 at 16:45, Tim Deegan <tim@xen.org> wrote:
> > At 15:37 +0000 on 24 Jan (1359041870), Jan Beulich wrote:
> >> >>> On 24.01.13 at 15:29, Tim Deegan <tim@xen.org> wrote:
> >> > At 17:25 -0800 on 11 Jan (1357925122), Mukesh Rathor wrote:
> >> >> diff -r bf249cd5f2c1 -r 278d7a933d88 xen/include/public/arch-x86/xen.h
> >> >> --- a/xen/include/public/arch-x86/xen.h Tue Oct 30 18:12:11 2012 +0000
> >> >> +++ b/xen/include/public/arch-x86/xen.h Fri Jan 11 16:19:40 2013 -0800
> >> >> @@ -157,7 +157,16 @@ struct vcpu_guest_context {
> >> >> struct cpu_user_regs user_regs; /* User-level CPU registers
> >
> >> > */
> >> >> struct trap_info trap_ctxt[256]; /* Virtual IDT
> >
> >> > */
> >> >> unsigned long ldt_base, ldt_ents; /* LDT (linear address, #
> > ents)
> >> > */
> >> >> - unsigned long gdt_frames[16], gdt_ents; /* GDT (machine frames, # ents)
> >
> >> > */
> >> >> + union {
> >> >> + struct {
> >> >> + /* GDT (machine frames, # ents) */
> >> >> + unsigned long gdt_frames[16], gdt_ents;
> >> >> + } pv;
> >> >> + struct {
> >> >> + /* PVH: GDTR addr and size */
> >> >> + unsigned long gdtaddr, gdtsz;
> >> >
> >> > The GDT size is always 16 bits; I'd be inclined to make the addr
> >> > explicitly 64 bits too, to help out 32-bit toolstacks.
> >> >
> >> >> + } pvh;
> >> >> + } u;
> >> >
> >> > Also, would you consider renaming this as:
> >> >
> >> > union {
> >> > struct {
> >> > /* GDT (machine frames, # ents) */
> >> > unsigned long frames[16], ents;
> >> > } pv;
> >> > struct {
> >> > /* PVH: GDTR addr and size */
> >> > unsigned long addr, sz;
> >> > } pvh;
> >> > } gdt;
> >> >
> >> > ? Then the calling code looks a little nicer.
> >>
> >> Did you overlook that it is a public header that gets modified
> >> here?
> >
> > No, but you already pointed that out so I didn't feel the need to. I'm
> > just suggesting that if we're going to change the naming here, we can
> > change it to something nicer.
>
> But we shouldn't change names or types here arbitrarily. It's
> one thing if something truly needs fixing, but another if it's merely
> cosmetic.
My comment about types was about a field that is added _in this patch_!
Likewise the renaming -- this patch already requires callers to
s/gdt_frames/u.pv.gdt_frames/g. Making it so users have to do
s/gdt_frames/gdt.pv.frames/g doesn't make that any worse.
Tim.
next prev parent reply other threads:[~2013-01-24 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 1:25 [RFC PATCH 1/15]: PVH xen: turn gdb_frames/gdt_ents into union Mukesh Rathor
2013-01-14 11:18 ` Jan Beulich
2013-01-15 0:45 ` Mukesh Rathor
2013-01-24 14:29 ` Tim Deegan
2013-01-24 15:37 ` Jan Beulich
2013-01-24 15:45 ` Tim Deegan
2013-01-24 15:54 ` Jan Beulich
2013-01-24 16:18 ` Tim Deegan [this message]
2013-01-25 2:04 ` Mukesh Rathor
2013-01-25 9:38 ` Tim Deegan
2013-01-25 10:23 ` 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=20130124161808.GI20551@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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).