From: Avi Kivity <avi@redhat.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Implement generic double fault generation mechanism
Date: Mon, 11 May 2009 09:17:40 +0300 [thread overview]
Message-ID: <4A07C304.2000208@redhat.com> (raw)
In-Reply-To: <9832F13BD22FB94A829F798DA4A8280501A81A9078@pdsmsx503.ccr.corp.intel.com>
Dong, Eddie wrote:
>> There is not point referring to current code. Current code does not
>> handle serial exceptions properly. So fix it in your patch otherwise I
>> propose to use my patch that fixes current code
>> (http://patchwork.kernel.org/patch/21829/).
>>
>>
>
> I would like Avi to decide.
I would prefer you two to reach agreement. Less work for me.
> I can check with internal architecture to see what does "handle exceptions serially" mean in really. For me serial means first in first out, and thus we should remain 1st exception.
>
The second exception was encountered while injecting the first
exception, so how can you continue with the first without servicing the
second?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-05-11 6:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:24 Implement generic double fault generation mechanism Dong, Eddie
2009-05-03 10:53 ` Gleb Natapov
2009-05-08 8:27 ` Dong, Eddie
2009-05-08 9:53 ` Gleb Natapov
2009-05-08 10:39 ` Dong, Eddie
2009-05-08 10:46 ` Dong, Eddie
2009-05-08 12:23 ` Gleb Natapov
2009-05-08 15:00 ` Dong, Eddie
2009-05-08 18:44 ` Gleb Natapov
2009-05-11 1:04 ` Dong, Eddie
2009-05-11 6:02 ` Gleb Natapov
2009-05-12 5:35 ` Dong, Eddie
2009-05-12 7:01 ` Gleb Natapov
2009-05-12 15:06 ` Enable IRQ windows after exception injection if there are pending virq Dong, Eddie
2009-05-12 15:27 ` Gleb Natapov
2009-05-13 7:45 ` Dong, Eddie
2009-05-13 10:29 ` Gleb Natapov
2009-05-13 14:05 ` Implement generic double fault generation mechanism Dong, Eddie
2009-05-11 6:17 ` Avi Kivity [this message]
2009-05-12 7:38 ` event injection MACROs Dong, Eddie
2009-05-12 8:49 ` Gleb Natapov
2009-05-13 9:49 ` Avi Kivity
2009-05-13 14:20 ` Dong, Eddie
2009-05-14 9:27 ` Avi Kivity
2009-05-14 13:43 ` Dong, Eddie
2009-05-14 14:16 ` Gleb Natapov
2009-05-14 14:34 ` Dong, Eddie
2009-05-14 15:44 ` Gleb Natapov
2009-05-15 7:57 ` Dong, Eddie
2009-05-17 9:44 ` Gleb Natapov
2009-05-08 12:16 ` Implement generic double fault generation mechanism Gleb Natapov
2009-05-08 8:19 ` Dong, Eddie
2009-05-08 8:28 ` 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=4A07C304.2000208@redhat.com \
--to=avi@redhat.com \
--cc=eddie.dong@intel.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.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