From: Joe Damato <ice799@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-x86_64@vger.kernel.org, w@1wt.eu, mingo@elte.hu,
jeremy@goop.org, linux-newbie@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: Add getter/setter static inlines for x86 descriptors
Date: Sun, 29 Mar 2009 14:50:39 -0700 [thread overview]
Message-ID: <3605561d0903291450v516a7e9csaff4309c0cacb121@mail.gmail.com> (raw)
In-Reply-To: <49CFE7E0.80500@zytor.com>
On Sun, Mar 29, 2009 at 2:28 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> Joe Damato wrote:
>> Static inline getters/setters have been provided to encourage consumers not to touch the internals of 32bit x86 descriptors directly.
>>
>> Signed-off-by: Joe Damato <ice799@gmail.com>
>
> Okay, what is the motivation for this?
>
> This is a serious question. The x86 descriptors are so complex that
> it's not clear to me that this restriction makes the code any more
> clear. Especially not with things like:
>
> - cpu->arch.gdt[i].b |= 0x00000100;
> + desc_set_hi(tmp, desc_get_hi(tmp) | 0x00000100);
>
> This isn't an improvement. If you're doing to so something like this,
> you need to actually implement the *intent* here.
Hi -
In my first patch set several months ago I replaced the structure
desc_struct with bit fields that exposed the fields for IDT/LDT/TSS
entries. This patch set was rejected for several reasons, one of which
was that Linux is trying to move away from bit fields. I also received
other comments such as "take a smaller bite", etc.
So instead of the bit fields, I implemented static inline
getters/setters. I thought that this small change would be a good
first step to re-test the waters of submitting patches to the kernel
before I started to clean out more pieces of the x86 architecture
specific code.
I agree that this isn't very clear, but from comments I received on my
first set, I assumed that this was closer to what people wanted to see
in the kernel. I am happy to iterate and submit something better, but
I am clearly misunderstanding what people would like to see.
Any suggestions on how this first-timer can help are greatly appreciated.
Joe
next prev parent reply other threads:[~2009-03-29 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 21:21 [PATCH 0/2] x86: Remove direct access to internal x86 descriptor fields Joe Damato
2009-03-29 21:21 ` [PATCH 1/2] x86: Add getter/setter static inlines for x86 descriptors Joe Damato
2009-03-29 21:21 ` [PATCH 2/2] x86: Replace direct access to descriptor fields with getter/setters Joe Damato
2009-03-29 21:28 ` [PATCH 1/2] x86: Add getter/setter static inlines for x86 descriptors H. Peter Anvin
2009-03-29 21:50 ` Joe Damato [this message]
2009-03-29 22:10 ` H. Peter Anvin
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=3605561d0903291450v516a7e9csaff4309c0cacb121@mail.gmail.com \
--to=ice799@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®