From: David Vrabel <dvrabel@cantab.net>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"Keir (Xen.org)" <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: x86_64: Fix off-by-one error setting up the Interrupt Stack Tables
Date: Wed, 09 May 2012 11:53:29 +0100 [thread overview]
Message-ID: <4FAA4CA9.6080702@cantab.net> (raw)
In-Reply-To: <1336559473.25514.64.camel@zakaz.uk.xensource.com>
On 09/05/12 11:31, Ian Campbell wrote:
> On Wed, 2012-05-09 at 11:22 +0100, Andrew Cooper wrote:
>> diff -r 8f1e0cc4a507 xen/include/asm-x86/processor.h
>> --- a/xen/include/asm-x86/processor.h
>> +++ b/xen/include/asm-x86/processor.h
>> @@ -424,7 +424,9 @@ struct tss_struct {
>> union { u64 rsp1, esp1; };
>> union { u64 rsp2, esp2; };
>> u64 reserved1;
>> - u64 ist[7];
>> + u64 ist[7]; /* Interrupt Stack Table is 1-based so tss->ist[0]
>> + * corresponds to an IST value of 1 in an Interrupt
>> + * Descriptor */
>
> Would it be too sneaky to drop "reserved1" and make ist be 8 elements?
> then ist[1] would actually be the slot corresponding to a value of 1 in
> an IDT entry.
We did discuss this briefly internally and I thought it would be too
sneaky. But perhaps it is ok if there is also #define IST_RESERVED 0
and a comment.
David
next prev parent reply other threads:[~2012-05-09 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 10:22 x86_64: Fix off-by-one error setting up the Interrupt Stack Tables Andrew Cooper
2012-05-09 10:31 ` Ian Campbell
2012-05-09 10:53 ` David Vrabel [this message]
2012-05-09 10:53 ` Andrew Cooper
2012-05-09 10:55 ` Jan Beulich
2012-05-09 11:00 ` Ian Campbell
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=4FAA4CA9.6080702@cantab.net \
--to=dvrabel@cantab.net \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--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 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.