public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: wangyanqing <Udknight@gmail.com>,
	torvalds@linux-foundation.org, castet.matthieu@free.fr,
	akpm@linux-foundation.org, x86@kernel.org, spock@gentoo.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86: remove NX from video bios area
Date: Thu, 17 Nov 2011 21:02:53 -0800	[thread overview]
Message-ID: <4EC5E6FD.8040902@zytor.com> (raw)
In-Reply-To: <20111118044515.GA17250@udknight.homenetwork>

On 11/17/2011 08:45 PM, wangyanqing wrote:
> Sorry for my bad idea!

Don't worry... the important thing is that we have a real problem and
we're trying to figure it out.

> Indeed v86d have double backend to execute x86 video bios code,
> one is lrmi(linux real mode interface), another is x86emu.Yesterday,
> I compile the v86d with x86emu.Below is the new maps:
> 
> 08048000-0805e000 r-xp 00000000 00:01 3324       /sbin/v86d 
> 0805e000-0805f000 rw-p 00015000 00:01 3324       /sbin/v86d 
> 0805f000-08060000 rw-p 00000000 00:00 0 
> b7713000-b7733000 rw-s 000e0000 00:01 3234       /dev/mem 
> b7733000-b7742000 rw-s 000c0000 00:01 3234       /dev/mem 
> b7742000-b7762000 rw-s 000a0000 00:01 3234       /dev/mem 
> b7762000-b7763000 rw-s 0009c000 00:01 3234       /dev/mem 
> b7763000-b7764000 rw-s 00000000 00:01 3234       /dev/mem 
> b7764000-b7784000 rw-p 00000000 00:01 3230       /dev/zero
> b7784000-b7785000 r-xp 00000000 00:00 0          [vdso]
> bf98a000-bf9ab000 rw-p 00000000 00:00 0          [stack]
> 
> As you see,  now v86d doesn't need the X permission.But 
> my machine still hang very early(verbose show uvesafb some 
> messages, then black screen, it hangs!)
> 
> But if I make the BIOS range X unconditionally, the problem is gone.
> So we need more hacky.Any comment is welcome.

Is there any way you can hook up a serial console to your machine?  I
suspect that we're getting a kernel panic that we're not seeing.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


      reply	other threads:[~2011-11-18  5:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  8:26 [PATCH v2] x86: remove NX from video bios area wangyanqing
2011-11-17 14:56 ` H. Peter Anvin
2011-11-18  4:45   ` wangyanqing
2011-11-18  5:02     ` H. Peter Anvin [this message]

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=4EC5E6FD.8040902@zytor.com \
    --to=hpa@zytor.com \
    --cc=Udknight@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=castet.matthieu@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spock@gentoo.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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