All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andi Kleen <ak@suse.de>,
	akpm@linux-foundation.org, bunk@stusta.de,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Cleanup: i386 separate hardware-defined TSS from Linux additions
Date: Thu, 29 Mar 2007 21:33:55 -0500	[thread overview]
Message-ID: <20070330023355.GU10459@waste.org> (raw)
In-Reply-To: <1175222195.12230.363.camel@localhost.localdomain>

On Fri, Mar 30, 2007 at 12:36:35PM +1000, Rusty Russell wrote:
> On Thu, 2007-03-29 at 13:16 +0200, Andi Kleen wrote:
> > Please clean it up properly with two structs.
> 
> Not sure about this, now I've done it.  Running it here.
> 
> If you like it, I can do x86-64 as well.
> 
> ==
> lguest defines its own TSS struct because the "struct tss_struct"
> contains linux-specific additions.  Andi asked me to split the struct
> in processor.h.
> 
> Unfortunately it makes usage a little awkward.
> 
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> 
> diff -r 7edfac26a523 include/asm-i386/processor.h
> --- a/include/asm-i386/processor.h	Thu Mar 29 20:02:17 2007 +1000
> +++ b/include/asm-i386/processor.h	Fri Mar 30 12:22:38 2007 +1000
> @@ -325,7 +325,8 @@ typedef struct {
>  
>  struct thread_struct;
>  
> -struct tss_struct {
> +/* This is the TSS defined by the hardware. */
> +struct i386_hw_tss {
>  	unsigned short	back_link,__blh;
>  	unsigned long	esp0;
>  	unsigned short	ss0,__ss0h;
> @@ -349,6 +350,11 @@ struct tss_struct {
>  	unsigned short	gs, __gsh;
>  	unsigned short	ldt, __ldth;
>  	unsigned short	trace, io_bitmap_base;
> +} __attribute__((packed));
> +
> +struct tss_struct {
> +	struct i386_hw_tss x86_tss;
> +
>  	/*
>  	 * The extra 1 is there because the CPU will access an
>  	 * additional byte beyond the end of the IO permission

This comment needs to stay in the first struct..?

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-03-30  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703270607.l2R672de009090@shell0.pdx.osdl.net>
     [not found] ` <200703291219.47276.ak@suse.de>
     [not found]   ` <1175165905.12230.201.camel@localhost.localdomain>
     [not found]     ` <200703291316.56393.ak@suse.de>
2007-03-30  2:36       ` [PATCH] Cleanup: i386 separate hardware-defined TSS from Linux additions Rusty Russell
2007-03-30  2:33         ` Matt Mackall [this message]
2007-03-30  5:44           ` Rusty Russell

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=20070330023355.GU10459@waste.org \
    --to=mpm@selenic.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.