From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Huang Ying <ying.huang@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Jin Dongming <jin.dongming@np.css.fujitsu.com>
Subject: Re: [PATCH 08/13] kvm: x86: Inject pending MCE events on state writeback
Date: Thu, 17 Feb 2011 16:17:27 -0200 [thread overview]
Message-ID: <20110217181727.GA12721@amt.cnet> (raw)
In-Reply-To: <4D5D6343.6060508@siemens.com>
On Thu, Feb 17, 2011 at 07:04:51PM +0100, Jan Kiszka wrote:
> >>> Should not manipulate mp_state of a running vcpu (should only do that
> >>> for migration when vcpu is stopped), since its managed by the kernel,
> >>> for irqchip case.
> >>
> >> Not for asynchronously injected MCEs. The target CPU would simply
> >> oversleep them. MCEs are not in the scope of the in-kernel irqchip.
> >
> > Pending MCE exception could break out of in-kernel halt emulation.
>
> Can't follow. What do you mean? That the kernel already takes care? I
> didn't find a trace, so I added that code.
Nevermind. This is rare and "halted -> running" transition in userspace
is harmless.
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>, Huang Ying <ying.huang@intel.com>,
Jin Dongming <jin.dongming@np.css.fujitsu.com>
Subject: [Qemu-devel] Re: [PATCH 08/13] kvm: x86: Inject pending MCE events on state writeback
Date: Thu, 17 Feb 2011 16:17:27 -0200 [thread overview]
Message-ID: <20110217181727.GA12721@amt.cnet> (raw)
In-Reply-To: <4D5D6343.6060508@siemens.com>
On Thu, Feb 17, 2011 at 07:04:51PM +0100, Jan Kiszka wrote:
> >>> Should not manipulate mp_state of a running vcpu (should only do that
> >>> for migration when vcpu is stopped), since its managed by the kernel,
> >>> for irqchip case.
> >>
> >> Not for asynchronously injected MCEs. The target CPU would simply
> >> oversleep them. MCEs are not in the scope of the in-kernel irqchip.
> >
> > Pending MCE exception could break out of in-kernel halt emulation.
>
> Can't follow. What do you mean? That the kernel already takes care? I
> didn't find a trace, so I added that code.
Nevermind. This is rare and "halted -> running" transition in userspace
is harmless.
next prev parent reply other threads:[~2011-02-17 18:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 8:23 [PATCH 00/13] [uq/master] Patch queue, part IV (MCE edition) Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 01/13] x86: Account for MCE in cpu_has_work Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 02/13] x86: Perform implicit mcg_status reset Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 03/13] x86: Small cleanups of MCE helpers Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 04/13] x86: Refine error reporting of MCE injection services Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 05/13] x86: Optionally avoid injecting AO MCEs while others are pending Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 06/13] Synchronize VCPU states before reset Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 07/13] kvm: x86: Move MCE functions together Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 08/13] kvm: x86: Inject pending MCE events on state writeback Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-17 16:35 ` Marcelo Tosatti
2011-02-17 16:35 ` [Qemu-devel] " Marcelo Tosatti
2011-02-17 17:06 ` Jan Kiszka
2011-02-17 17:06 ` [Qemu-devel] " Jan Kiszka
2011-02-17 17:55 ` Marcelo Tosatti
2011-02-17 17:55 ` [Qemu-devel] " Marcelo Tosatti
2011-02-17 18:04 ` Jan Kiszka
2011-02-17 18:04 ` [Qemu-devel] " Jan Kiszka
2011-02-17 18:17 ` Marcelo Tosatti [this message]
2011-02-17 18:17 ` Marcelo Tosatti
2011-02-15 8:23 ` [PATCH 09/13] kvm: x86: Consolidate TCG and KVM MCE injection code Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-17 18:08 ` Marcelo Tosatti
2011-02-17 18:08 ` [Qemu-devel] " Marcelo Tosatti
2011-02-17 18:17 ` Jan Kiszka
2011-02-17 18:17 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 10/13] kvm: x86: Clean up kvm_setup_mce Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 11/13] kvm: x86: Fail kvm_arch_init_vcpu if MCE initialization fails Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 12/13] Add qemu_ram_remap Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
2011-02-15 8:23 ` [PATCH 13/13] KVM, MCE, unpoison memory address across reboot Jan Kiszka
2011-02-15 8:23 ` [Qemu-devel] " Jan Kiszka
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=20110217181727.GA12721@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=ying.huang@intel.com \
/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.