From: Jan Kiszka <jan.kiszka@web.de>
To: Richard Henderson <rth@twiddle.net>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 0/8] cpu interrupt cleanup
Date: Sun, 01 May 2011 10:18:37 +0200 [thread overview]
Message-ID: <4DBD175D.4080608@web.de> (raw)
In-Reply-To: <4DBC8F01.9020109@twiddle.net>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
On 2011-05-01 00:36, Richard Henderson wrote:
> Also, the i386 port defines a CPU_TARGET_MCE, checked by the kvm code,
> but as far as I can tell that bit is never set. I've left that alone
> for now.
That rather looks like a ghost. Can you name some hashes, files, and
lines that should contain this?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-05-01 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 22:24 [Qemu-devel] [PATCH 0/8] cpu interrupt cleanup Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 1/8] irq: Introduce CPU_INTERRUPT_TGT_* defines Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 2/8] irq: Introduce and use CPU_INTERRUPT_SSTEP_MASK Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 3/8] target-mips: Do not check CPU_INTERRUPT_TIMER Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 4/8] target-sparc: " Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 5/8] irq: Remove CPU_INTERRUPT_TIMER Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 6/8] target-arm: Privatize CPU_INTERRUPT_FIQ Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 7/8] target-i386: Privatize some i386-specific interrupt names Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 8/8] irq: Privatize CPU_INTERRUPT_NMI Richard Henderson
2011-04-30 22:36 ` [Qemu-devel] [PATCH 0/8] cpu interrupt cleanup Richard Henderson
2011-05-01 8:18 ` Jan Kiszka [this message]
2011-05-01 14:59 ` Richard Henderson
2011-05-01 17:31 ` Jan Kiszka
2011-05-04 19:19 ` 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=4DBD175D.4080608@web.de \
--to=jan.kiszka@web.de \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).