From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: Convert INIT and SIPI signals into synchronously handled events
Date: Wed, 13 Mar 2013 10:08:13 +0100 [thread overview]
Message-ID: <514041FD.4050107@siemens.com> (raw)
In-Reply-To: <514040CB.3070704@redhat.com>
On 2013-03-13 10:03, Paolo Bonzini wrote:
> Il 13/03/2013 08:39, Jan Kiszka ha scritto:
>>> I think this should clear pending SIPIs, unless KVM_APIC_INIT
>>> was already set in which case it should be a no-op. Something
>>> like:
>>>
>>> e = apic->pending_events; while (!(e & KVM_APIC_INIT)) e =
>>> cmpxchg(&apic->pending_events, e, (e | KVM_APIC_INIT) &
>>> ~KVM_APIC_SIPI);
>>>
>>> If you do this, better make pending_events an atomic_t.
>
>> Quick question: Why atomic_t? It becomes a bit ugly to poke into
>> the atomic counter for bitops, and cmpxchg is mapped on an
>> interlocked version.
>
> It's a bit safer because it forces you to use atomic_read, and
> generally points out to reviewers to think about memory barriers. But
> indeed the lack of atomic_set_bit and atomic_clear_bit makes the code
> uglier. And as long as there are no other bits in
> apic->pending_events, the above loop is actually the same as just
>
> apic->pending_events = 1 << KVM_APIC_INIT;
Yeah, can simplify this in the next version of the just posted patch.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-03-13 9:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 11:44 [PATCH] KVM: x86: Convert INIT and SIPI signals into synchronously handled events Jan Kiszka
2013-03-12 12:06 ` Paolo Bonzini
2013-03-12 12:29 ` Gleb Natapov
2013-03-12 12:29 ` Paolo Bonzini
2013-03-12 12:46 ` Jan Kiszka
2013-03-12 12:49 ` Gleb Natapov
2013-03-12 12:52 ` Jan Kiszka
2013-03-12 12:53 ` Gleb Natapov
2013-03-12 13:09 ` Paolo Bonzini
2013-03-12 13:13 ` Jan Kiszka
2013-03-12 12:58 ` Jan Kiszka
2013-03-12 13:01 ` Jan Kiszka
2013-03-12 13:13 ` Paolo Bonzini
2013-03-12 13:16 ` Jan Kiszka
2013-03-12 13:25 ` Gleb Natapov
2013-03-12 13:27 ` Jan Kiszka
2013-03-12 13:37 ` Gleb Natapov
2013-03-13 7:39 ` Jan Kiszka
2013-03-13 9:03 ` Paolo Bonzini
2013-03-13 9:08 ` Jan Kiszka [this message]
2013-03-12 13:12 ` Gleb Natapov
2013-03-12 13:21 ` Jan Kiszka
2013-03-12 13:41 ` Gleb Natapov
2013-03-12 13:43 ` Paolo Bonzini
2013-03-12 13:52 ` Gleb Natapov
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=514041FD.4050107@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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.