From: "Alex Bennée" <alex.bennee@linaro.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: mttcg@listserver.greensocs.com, claudio.fontana@huawei.com,
Alvise Rigo <a.rigo@virtualopensystems.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com,
jani.kokkonen@huawei.com, tech@virtualopensystems.com
Subject: Re: [Qemu-devel] [RFC v4 5/9] configure: Enable/disable new qemu_{ld, st} excl insns
Date: Sun, 09 Aug 2015 17:27:52 +0100 [thread overview]
Message-ID: <87y4hkl94n.fsf@linaro.org> (raw)
In-Reply-To: <20150809101310.GB5883@aurel32.net>
Aurelien Jarno <aurelien@aurel32.net> writes:
> On 2015-08-09 10:51, Alex Bennée wrote:
>>
>> Aurelien Jarno <aurelien@aurel32.net> writes:
>>
>> > On 2015-08-09 09:11, Alex Bennée wrote:
>> >>
>> >> Aurelien Jarno <aurelien@aurel32.net> writes:
>> >>
>> >> > On 2015-08-07 19:03, Alvise Rigo wrote:
>> >> >> Introduce the new --enable-tcg-ldst-excl configure option to enable the
>> >> >> LL/SC operations only for those backends that support them.
>> >> >>
>> >> >> Suggested-by: Jani Kokkonen <jani.kokkonen@huawei.com>
>> >> >> Suggested-by: Claudio Fontana <claudio.fontana@huawei.com>
>> >> >> Signed-off-by: Alvise Rigo <a.rigo@virtualopensystems.com>
>> >> >> ---
>> >> >> configure | 21 +++++++++++++++++++++
>> >> >> 1 file changed, 21 insertions(+)
>> >> >
>> >> > We have seen that for this kind of patch, it's better to add support in
>> >> > all backends, otherwise it takes ages to get all the backends converted.
>> >> > I think you should involve the backend maintainers. I can try to provide
>> >> > the corresponding patches for mips and ia64.
>> >>
>> >> We discussed this on the last MTTCG call and agree. However we will need
>> >> help from the other TCG maintainers for the backends. The changes should
>> >> be fairly mechanical though.
>> >>
>> >> However in the spirit of keeping trees building in the meantime should
>> >> we change this from a configure option to just a static option for each
>> >> given backend as it is converted?
>> >
>> > I am not even sure we need a static option. I guess providing we are
>> > doing that early enough in the 2.5 cycle, we can just add the new ops
>> > and start using them. Of course we should put the backends maintainers
>> > in the loop so they can fix that quickly and don't get a surprise weeks
>> > afters.
>> >
>> > That said, please see my other email, I am not sure we actually need to
>> > modify backends, I think we can implement these new "ops" through
>> > tcg-runtime.
>>
>> We still need to ensure "normal" ld/st operations trip the exclusive bit
>> though.
>
> Isn't that taken care of by the TLB_EXCL flag, causing pages in
> exclusive mode to always go through the slow path? Then we should not
> need to modify the backends as they already check for non zero bits in
> this area.
Ahh I see. Yes of course that sounds like a good idea.
--
Alex Bennée
next prev parent reply other threads:[~2015-08-09 16:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 17:03 [Qemu-devel] [RFC v4 0/9] Slow-path for atomic instruction translation Alvise Rigo
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 1/9] exec.c: Add new exclusive bitmap to ram_list Alvise Rigo
2015-08-11 13:52 ` Paolo Bonzini
2015-08-11 14:24 ` Peter Maydell
2015-08-11 14:34 ` alvise rigo
2015-08-11 15:54 ` alvise rigo
2015-08-11 15:55 ` Paolo Bonzini
2015-08-11 16:11 ` alvise rigo
2015-08-11 16:32 ` Paolo Bonzini
2015-08-12 7:31 ` alvise rigo
2015-08-12 12:36 ` Paolo Bonzini
2015-08-12 13:02 ` Peter Maydell
2015-08-12 14:04 ` alvise rigo
2015-08-12 14:10 ` Paolo Bonzini
2015-08-12 14:32 ` alvise rigo
2015-09-10 13:04 ` alvise rigo
2015-09-10 16:19 ` Alex Bennée
2015-09-10 17:36 ` alvise rigo
2015-09-10 16:25 ` Paolo Bonzini
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 2/9] softmmu: Add new TLB_EXCL flag Alvise Rigo
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 3/9] softmmu: Add helpers for a new slowpath Alvise Rigo
2015-08-11 13:32 ` alvise rigo
2015-08-11 13:52 ` Paolo Bonzini
2015-08-11 15:55 ` alvise rigo
2015-08-12 12:43 ` Paolo Bonzini
2015-08-12 13:09 ` alvise rigo
2015-08-12 13:14 ` Paolo Bonzini
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 4/9] tcg-op: create new TCG qemu_{ld, st} excl variants Alvise Rigo
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 5/9] configure: Enable/disable new qemu_{ld, st} excl insns Alvise Rigo
2015-08-08 12:44 ` Aurelien Jarno
2015-08-08 13:57 ` Peter Maydell
2015-08-09 8:11 ` Alex Bennée
2015-08-09 8:40 ` Aurelien Jarno
2015-08-09 9:51 ` Alex Bennée
2015-08-09 10:13 ` Aurelien Jarno
2015-08-09 16:27 ` Alex Bennée [this message]
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 6/9] tcg-i386: Implement excl variants of qemu_{ld, st} Alvise Rigo
2015-08-08 13:00 ` Aurelien Jarno
2015-08-10 7:50 ` alvise rigo
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 7/9] tcg-arm: " Alvise Rigo
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 8/9] tcg-aarch64: " Alvise Rigo
2015-08-07 17:03 ` [Qemu-devel] [RFC v4 9/9] target-arm: translate: Use ld/st excl for atomic insns Alvise Rigo
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=87y4hkl94n.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=a.rigo@virtualopensystems.com \
--cc=aurelien@aurel32.net \
--cc=claudio.fontana@huawei.com \
--cc=jani.kokkonen@huawei.com \
--cc=mttcg@listserver.greensocs.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).