qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH, RFT] monitor: implement x86 info tlb for PAE and long modes
Date: Mon, 6 Dec 2010 18:38:10 +0000	[thread overview]
Message-ID: <AANLkTims1V-Xc88HnaeWhHZ2XZN3prPw-QOQXwXz3prA@mail.gmail.com> (raw)
In-Reply-To: <0BD7805E-DFCF-4751-A6FF-EFAD361C0998@suse.de>

On Mon, Dec 6, 2010 at 11:12 AM, Alexander Graf <agraf@suse.de> wrote:
>
> On 05.12.2010, at 17:25, Blue Swirl wrote:
>
>> 'info tlb' didn't show correct information for PAE mode and
>> x86_64 long mode.
>>
>> Implement the missing modes. Also print NX bit for PAE and long modes.
>> Fix off-by-one error in 32 bit mode mask.
>>
>> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
>> ---
>>
>> I didn't find an OS that enabled PAE, please test and report.
>
> Xen does. Just take a random recent xen kernel and run it with -kernel :).

Thanks, it does (CR4 is 0xb0). I'm not sure all is correct, after
0x1000000 the dump looks messy:
0000000000c00000: 0000000000c00000 --PDA---W
0000000000e00000: 0000000000e00000 --PDA---W
0000000001000000: f000ff53f000f000 XG-D-C--W
0000000001001000: f000ff53f000e000 X--D----W
0000000001002000: f000ff53f000f000 XG-D-C--W
0000000001003000: f000ff53f000f000 XG-D-C--W
0000000001004000: f000e987f000f000 X---A--U-

  parent reply	other threads:[~2010-12-06 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 16:25 [Qemu-devel] [PATCH, RFT] monitor: implement x86 info tlb for PAE and long modes Blue Swirl
2010-12-06 11:12 ` Alexander Graf
2010-12-06 13:05   ` Ian Campbell
2010-12-06 18:41     ` Blue Swirl
2010-12-07 10:05       ` Ian Campbell
2010-12-06 18:38   ` Blue Swirl [this message]
2010-12-07 10:08     ` Alexander Graf
2010-12-11  9:34       ` Blue Swirl

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=AANLkTims1V-Xc88HnaeWhHZ2XZN3prPw-QOQXwXz3prA@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.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).