From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: Andrew Morton <akpm@osdl.org>,
virtualization@lists.osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 2/4] x86 paravirt_ops: paravirt_desc.h for native descriptor ops.
Date: Mon, 7 Aug 2006 13:19:58 -0400 [thread overview]
Message-ID: <20060807171958.GT13393@redhat.com> (raw)
In-Reply-To: <200608071053.28293.ak@muc.de>
On Mon, Aug 07, 2006 at 10:53:28AM +0200, Andi Kleen wrote:
> On Monday 07 August 2006 09:50, Rusty Russell wrote:
> > On Mon, 2006-08-07 at 07:40 +0200, Andi Kleen wrote:
> > > On Monday 07 August 2006 06:45, Rusty Russell wrote:
> > > > Unfortunately, due to include cycles, we can't put these in
> > > > paravirt.h: we use a separate header for these.
> > > >
> > > > The implementation comes from Zach's [RFC, PATCH 10/24] i386 Vmi descriptor changes:
> > > >
> > > > Descriptor and trap table cleanups. Add cleanly written accessors for
> > > > IDT and GDT gates so the subarch may override them. Note that this
> > > > allows the hypervisor to transparently tweak the DPL of the descriptors
> > > > as well as the RPL of segments in those descriptors, with no unnecessary
> > > > kernel code modification. It also allows the hypervisor implementation
> > > > of the VMI to tweak the gates, allowing for custom exception frames or
> > > > extra layers of indirection above the guest fault / IRQ handlers.
> > >
> > > Nice cleanup. The old assembly mess was ripe to be killed for a long time.
> >
> > OK, here's that patch extracted out.
>
> Is there something wrong with your mailer? This one doesn't apply either:
Looks like it's against Linus' tree, not whatever you were trying against...
(13:19:10:davej@nwo:linux-2.6)$ cat ~/rusty | patch -p1 --dry-run
patching file arch/i386/kernel/traps.c
Hunk #1 succeeded at 1116 (offset 4 lines).
Hunk #3 succeeded at 1132 (offset 4 lines).
patching file include/asm-i386/desc.h
(13:19:15:davej@nwo:linux-2.6)$
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-07 17:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 4:43 [PATCH 1/4] x86 paravirt_ops: create no_paravirt.h for native ops Rusty Russell
2006-08-07 4:45 ` [PATCH 2/4] x86 paravirt_ops: paravirt_desc.h for native descriptor ops Rusty Russell
2006-08-07 4:47 ` [PATCH 3/4] x86 paravirt_ops: implementation of paravirt_ops Rusty Russell
2006-08-07 4:48 ` [PATCH 4/4] x86 paravirt_ops: binary patching infrastructure Rusty Russell
2006-08-07 5:14 ` Rusty Russell
2006-08-07 5:38 ` Andi Kleen
2006-08-07 5:56 ` Jeremy Fitzhardinge
2006-08-07 5:39 ` [PATCH 3/4] x86 paravirt_ops: implementation of paravirt_ops Andi Kleen
2006-08-07 5:56 ` Jeremy Fitzhardinge
2006-08-07 6:13 ` Rusty Russell
2006-08-07 6:20 ` Andi Kleen
2006-08-07 7:27 ` Rusty Russell
2006-08-07 5:40 ` [PATCH 2/4] x86 paravirt_ops: paravirt_desc.h for native descriptor ops Andi Kleen
2006-08-07 7:50 ` Rusty Russell
2006-08-07 8:53 ` Andi Kleen
2006-08-07 17:19 ` Dave Jones [this message]
2006-08-07 5:22 ` [PATCH 1/4] x86 paravirt_ops: create no_paravirt.h for native ops Jeremy Fitzhardinge
2006-08-07 5:30 ` Andi Kleen
2006-08-07 5:43 ` Jeremy Fitzhardinge
2006-08-07 6:02 ` Andi Kleen
2006-08-07 6:23 ` Jeremy Fitzhardinge
2006-08-07 6:03 ` Rusty Russell
2006-08-07 6:16 ` Andi Kleen
2006-08-07 6:04 ` Rusty Russell
2006-08-07 6:17 ` Andi Kleen
2006-08-07 6:27 ` Muli Ben-Yehuda
2006-08-07 7:34 ` Jan Engelhardt
2006-08-07 8:40 ` Muli Ben-Yehuda
2006-08-07 17:54 ` Jan Engelhardt
2006-08-07 20:51 ` Zachary Amsden
2006-08-08 1:59 ` Andi Kleen
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=20060807171958.GT13393@redhat.com \
--to=davej@redhat.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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).