From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Kiselev,
Sergey" <sergey.kiselev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Writing to MCG_STATUS register
Date: Thu, 22 Mar 2007 13:47:00 +0200 [thread overview]
Message-ID: <46026CB4.4090607@qumranet.com> (raw)
In-Reply-To: <C07C4589BE74A34981C3C3525EE1F80101A7A177-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Kiselev, Sergey wrote:
> Hi,
>
> Some older (~2.6.7) kernels write MCG_STATUS register during kernel
> boot (mce_clear_all() function, called from mce_init()). It's not
> currently handled by kvm and will cause it to inject a GPF.
> Following patch adds a "nop" handler for this:
>
Your email client mangles whitespace. Please resend as attachment.
Also, please add a Signed-off-by: line.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-22 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 11:41 Writing to MCG_STATUS register Kiselev, Sergey
[not found] ` <C07C4589BE74A34981C3C3525EE1F80101A7A177-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-03-22 11:47 ` Avi Kivity [this message]
[not found] ` <46026CB4.4090607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-22 11:59 ` [PATCH] " Kiselev, Sergey
[not found] ` <C07C4589BE74A34981C3C3525EE1F80101A7A1AA-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-03-22 12:06 ` Avi Kivity
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=46026CB4.4090607@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sergey.kiselev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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