From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
christoffer dall <christoffer.dall@linaro.org>,
marc zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH kvm-unit-tests] arm: fix crash when caches are off
Date: Tue, 16 Sep 2014 14:28:57 +0200 [thread overview]
Message-ID: <54182D09.9000700@redhat.com> (raw)
In-Reply-To: <198129286.4990140.1410869523048.JavaMail.zimbra@redhat.com>
Il 16/09/2014 14:12, Andrew Jones ha scritto:
>> > Should it at least write 1 to the spinlock?
> I thought about that. So on one hand we might get a somewhat functional
> synchronization mechanism, which may be enough for some unit test that
> doesn't enable caches, but still needs it. On the other hand, we know
> its broken, so we don't really want any unit tests that need synchronization
> and don't enable caches. I chose to not write a 1 in the hope that if
> a unit test introduces a race, that that race will be easier to expose
> and fix. That said, I'm not strongly biased, as we'd still have a race,
> which may or may not be easy to expose, either way. So if the majority
> prefers a best effort approach, then I'll spin a v2.
The case I was thinking about was something like
spin_lock()
enable caches
start other processors
spin_unlock()
I'm not sure if it makes sense though. :)
Paolo
next prev parent reply other threads:[~2014-09-16 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 2:06 [PATCH kvm-unit-tests] arm: fix crash when caches are off Andrew Jones
2014-09-16 8:14 ` Paolo Bonzini
2014-09-16 12:12 ` Andrew Jones
2014-09-16 12:28 ` Paolo Bonzini [this message]
2014-09-16 12:43 ` Andrew Jones
2014-09-16 12:47 ` Paolo Bonzini
2014-09-16 12:51 ` Andrew Jones
2014-09-16 14:38 ` Andrew Jones
2014-09-16 18:04 ` Andrew Jones
2014-09-16 12:57 ` Andrew Jones
2014-09-26 7:51 ` Christoffer Dall
2014-10-30 15:59 ` Andrew Jones
2014-09-16 12:48 ` Andrew Jones
2014-09-18 10:36 ` Paolo Bonzini
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=54182D09.9000700@redhat.com \
--to=pbonzini@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.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.