From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Stas Sergeev <stsp@aknet.ru>, linux-kernel@vger.kernel.org
Subject: Re: [patch] espfix cleanup take 2
Date: Wed, 02 Aug 2006 22:06:07 -0700 [thread overview]
Message-ID: <44D1843F.9090309@vmware.com> (raw)
In-Reply-To: <20060802203336.c4f8a428.akpm@osdl.org>
Andrew Morton wrote:
> On Wed, 02 Aug 2006 20:43:47 +0400
> Stas Sergeev <stsp@aknet.ru> wrote:
>
>
>> Attached is a new espfix cleanup patch.
>>
>
> Ho hum, this conflicts moderately with the hypervisor preparatory patches
> which Jeremy sent.
>
> So could I ask that you redo this patch in a couple of weeks time against
> the current -mm lineup? I'd prefer not to merge it immediately because
> doing so would make it even harder than usual to work out who to blame if
> things break ;)
>
That would be my preference as well - I don't really have the bandwidth
to do a full review / test and integration of Stas's patch right now.
Subtle isn't really the word for this change - NMIs, debug handling,
sysenter, kernel stack copying, segment registers, interrupts, kernel
exception fixup, 16-bit stacks, descriptor tables and now CFI
annotations all come into play. Basically, all the evil and tricky
parts of i386 all come out to play together, and the control flow is
non-linear in places. Sadomasochistic is a more appropriate word. But
it is a very nice change, and I would like to see it merged into -mm
eventually. I actually have an ad-hoc test suite that tests most of
these paths, but I've never gotten formal and rigorous enough with it to
publish. I'll see if I can do that sometime in the next two weeks ;)
Zach
next prev parent reply other threads:[~2006-08-03 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 16:43 [patch] espfix cleanup take 2 Stas Sergeev
2006-08-03 3:33 ` Andrew Morton
2006-08-03 5:06 ` Zachary Amsden [this message]
2006-09-30 18:18 ` [patch] espfix cleanup take 3 Stas Sergeev
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=44D1843F.9090309@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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