From: Michael Tokarev <mjt@tls.msk.ru>
To: Tobias Markus <tobias@markus-regensburg.de>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
"Richard Henderson" <rth@twiddle.net>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-trivial] [Qemu-devel] PING Re: [PATCH v3] target-i386: Fix segment cache dump
Date: Sat, 14 Sep 2013 13:23:28 +0400 [thread overview]
Message-ID: <52342B10.5020708@msgid.tls.msk.ru> (raw)
In-Reply-To: <52331BA9.4000906@markus-regensburg.de>
13.09.2013 18:05, Tobias Markus wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/25/2013 12:20 PM, Tobias Markus wrote:
>> When in Long Mode, cpu_x86_seg_cache() logs "DS16" because the
>> Default operation size bit (D/B bit) is not set for Long Mode Data
>> Segments since there are only Data Segments in Long Mode and no
>> explicit 16/32/64-bit Descriptors. This patch fixes this by
>> checking the Long Mode Active bit of the hidden flags variable and
>> logging "DS" if it is set. (I.e. in Long Mode all Data Segments are
>> logged as "DS")
Thanks, applied to the trivial-patches queue.
Andreas: if you think it should go to i386 queue instead please
just reply to this email saying so, before I'll send a pull request
to Anthony. Before a pull request it is really trivial to remove
one patch from a queue.
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Tobias Markus <tobias@markus-regensburg.de>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
"Richard Henderson" <rth@twiddle.net>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Qemu-trivial] PING Re: [PATCH v3] target-i386: Fix segment cache dump
Date: Sat, 14 Sep 2013 13:23:28 +0400 [thread overview]
Message-ID: <52342B10.5020708@msgid.tls.msk.ru> (raw)
In-Reply-To: <52331BA9.4000906@markus-regensburg.de>
13.09.2013 18:05, Tobias Markus wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/25/2013 12:20 PM, Tobias Markus wrote:
>> When in Long Mode, cpu_x86_seg_cache() logs "DS16" because the
>> Default operation size bit (D/B bit) is not set for Long Mode Data
>> Segments since there are only Data Segments in Long Mode and no
>> explicit 16/32/64-bit Descriptors. This patch fixes this by
>> checking the Long Mode Active bit of the hidden flags variable and
>> logging "DS" if it is set. (I.e. in Long Mode all Data Segments are
>> logged as "DS")
Thanks, applied to the trivial-patches queue.
Andreas: if you think it should go to i386 queue instead please
just reply to this email saying so, before I'll send a pull request
to Anthony. Before a pull request it is really trivial to remove
one patch from a queue.
/mjt
next prev parent reply other threads:[~2013-09-14 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 10:20 [Qemu-devel] [PATCH v3] target-i386: Fix segment cache dump Tobias Markus
2013-08-26 17:38 ` Richard Henderson
2013-09-13 14:05 ` [Qemu-trivial] [Qemu-devel] PING " Tobias Markus
2013-09-13 14:05 ` Tobias Markus
2013-09-14 9:23 ` Michael Tokarev [this message]
2013-09-14 9:23 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2013-09-13 14:21 ` [Qemu-trivial] [Qemu-devel] " Tobias Markus
2013-09-13 14:21 ` Tobias Markus
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=52342B10.5020708@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
--cc=tobias@markus-regensburg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.