From: Alexander Graf <agraf@suse.de>
To: kvm-ppc@vger.kernel.org
Subject: Re: re-writing on powerpc
Date: Tue, 14 Dec 2010 17:48:18 +0000 [thread overview]
Message-ID: <4D07ADE2.3030707@suse.de> (raw)
In-Reply-To: <FD1A71B048BD854792EE753E0E9F27DE80A7@az33exm20>
Scott Wood wrote:
> On Tue, 14 Dec 2010 01:24:50 +0100
> Alexander Graf <alex@csgraf.de> wrote:
>
>
>> On 14.12.2010, at 01:18, Scott Wood wrote:
>>
>>
>>> Right, but I'm not talking about an interrupt that happens when the
>>> virtual EE bit is zero. I'm talking about an interrupt that happens
>>> right in the middle of the paravirt sequence -- after reading int_pending,
>>> but before setting critical to r2.
>>>
>>> It seems like the race window is just narrowed, not eliminated.
>>>
>> Hrm, is that window really that important? There's usually plenty of interrupts and mmios coming through to always have some check going on.
>>
>
> It could be important for realtime loads, tickless systems (especially
> if the Linux host eventually grows the ability to be tickless even
> when things are running), etc., and it makes me nervous in general.
>
> It's not something that's going to be causing problems all the time,
> though.
>
I agree - it's certainly wrong.
>> If it really is important, we could also check int_pending right after the critical section and just do a nop exit.
>>
>
> Doesn't checking int_pending require clobbering registers, which is why
> we have the critical section in the first place?
>
The critical section is to prevent us from overwriting the scratch
registers, yeah. And I think you're right - I had a thinko last night.
If we see that we should inject an interrupt, but we're inside of a
critical section, we could set the magic page to r/o and try to find the
critical end at which point we can just inject.
>
>> That way we worst case waste a few cycles for the useless guest exit,
>> but always fetch interrupts immediately when they occur.
>>
>
> What useless guest exit? Either we exit when we see an interrupt
> pending (in which case it's not useless), or we exit all the time, and
> then what's the point of the paravirt?
>
I was thinking of a case where we get a few false positives. But again,
I probably just had a bad thought :)
Alex
next prev parent reply other threads:[~2010-12-14 17:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 4:45 re-writing on powerpc Yoder Stuart-B08248
2010-12-13 8:35 ` Avi Kivity
2010-12-13 8:42 ` Alexander Graf
2010-12-13 8:45 ` Avi Kivity
2010-12-13 17:12 ` Hollis Blanchard
2010-12-13 17:15 ` Avi Kivity
2010-12-13 17:17 ` Hollis Blanchard
2010-12-13 19:03 ` Scott Wood
2010-12-13 23:54 ` Alexander Graf
2010-12-14 0:18 ` Scott Wood
2010-12-14 0:24 ` Alexander Graf
2010-12-14 8:40 ` Avi Kivity
2010-12-14 8:42 ` Avi Kivity
2010-12-14 8:48 ` Avi Kivity
2010-12-14 9:08 ` Alexander Graf
2010-12-14 15:45 ` Yoder Stuart-B08248
2010-12-14 15:48 ` Avi Kivity
2010-12-14 16:55 ` Scott Wood
2010-12-14 17:48 ` Alexander Graf [this message]
2010-12-14 17:53 ` Hollis Blanchard
2010-12-14 18:37 ` Scott Wood
2010-12-14 18:41 ` Scott Wood
2010-12-14 20:04 ` Scott Wood
2010-12-14 23:00 ` Alexander Graf
2010-12-14 23:17 ` Scott Wood
2010-12-14 23:29 ` Alexander Graf
2010-12-15 0:00 ` Scott Wood
2010-12-15 0:13 ` Alexander Graf
2010-12-15 0:57 ` Andreas Färber
2010-12-15 9:48 ` Avi Kivity
2010-12-15 11:16 ` Sethi Varun-B16395
2010-12-15 11:18 ` Avi Kivity
2010-12-15 11:32 ` Sethi Varun-B16395
2010-12-15 12:25 ` Avi Kivity
2010-12-17 21:59 ` Benjamin Herrenschmidt
2010-12-17 22:00 ` Benjamin Herrenschmidt
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=4D07ADE2.3030707@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@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 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.