From: Harvey Harrison <harvey.harrison@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] x86: Use v8086_mode helper, trivial unification
Date: Fri, 18 Jan 2008 01:22:00 -0800 [thread overview]
Message-ID: <1200648120.5724.131.camel@brick> (raw)
In-Reply-To: <20080118091208.GE24337@elte.hu>
On Fri, 2008-01-18 at 10:12 +0100, Ingo Molnar wrote:
> * Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
> > Use v8086_mode inline in fault_32.c, no functional change also ifdef
> > the section for 32-bit only and add to fault_64.c
>
> > - if (regs->flags & VM_MASK) {
> > + if (v8086_mode(regs)) {
>
> > --- a/arch/x86/mm/fault_64.c
> > +++ b/arch/x86/mm/fault_64.c
> > @@ -551,6 +551,16 @@ good_area:
> > tsk->maj_flt++;
> > else
> > tsk->min_flt++;
> > +
> > + /*
> > + * Did it hit the DOS screen memory VA from vm86 mode?
> > + */
> > + if (v8086_mode(regs)) {
> > + unsigned long bit = (address - 0xA0000) >> PAGE_SHIFT;
> > + if (bit < 32)
> > + tsk->thread.screen_bitmap |= 1 << bit;
> > + }
>
> hm, is there even vm86 mode in 64-bit? Anyway, gcc will eliminate it i
> guess. I've applied your patch.
>
No, it doesn't mean anything to 64-bit, but helps make the diff a little
bit smaller, getting pretty close now.
Still needs a bit of work to introduce oops_begin/end from 64-bit to
32-bit in traps_32.c and introduce a bad_pgtable-like function to
32bit, then we're down to small differences between 32/64 bit
do_page_fault and vmalloc_sync_all that should be relatively clean
to harmonize.
Got distracted with the ptrace stuff today, but patch coming soon.
Harvey
next prev parent reply other threads:[~2008-01-18 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 0:25 Harvey Harrison
2008-01-18 9:12 ` Ingo Molnar
2008-01-18 9:22 ` Harvey Harrison [this message]
2008-01-18 15:00 ` Ingo Molnar
2008-01-18 19:04 ` Harvey Harrison
2008-01-18 19:02 ` 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=1200648120.5724.131.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
Powered by JetHome