From: Richard Henderson <richard.henderson@linaro.org>
To: Taylor Simpson <tsimpson@quicinc.com>,
Richard Henderson <rth@twiddle.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] Add support for a helper with 7 arguments
Date: Fri, 7 Feb 2020 08:53:19 +0000 [thread overview]
Message-ID: <858bff3f-6e24-20a7-a7f3-49bee2cb8e12@linaro.org> (raw)
In-Reply-To: <BYAPR02MB488682AB2538F8EBE631EA80DE1C0@BYAPR02MB4886.namprd02.prod.outlook.com>
On 2/7/20 4:46 AM, Taylor Simpson wrote:
>> I think that we can do the store immediately -- I give specifics above. Do you
>> have a counter-example? Admittedly I'm new to browsing the architecture,
>> but I
>> don't see a legal packet for which you can't just Store Now.
>
> You can have two stores in a packet, and the second one could fault. If anything in the packet faults, none of the instructions commit.
Then what does the manual mean when it says "dual stores have non-parallel
semantics"? Is that solely about the semantics of the bytes in memory?
r~
next prev parent reply other threads:[~2020-02-07 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 22:41 [PATCH] Add support for a helper with 7 arguments Taylor Simpson
2020-02-06 6:02 ` Richard Henderson
2020-02-06 10:28 ` Richard Henderson
2020-02-06 14:03 ` Taylor Simpson
2020-02-06 15:35 ` Richard Henderson
2020-02-06 17:52 ` Taylor Simpson
2020-02-07 0:27 ` Richard Henderson
2020-02-07 4:46 ` Taylor Simpson
2020-02-07 8:53 ` Richard Henderson [this message]
2020-02-07 11:59 ` Taylor Simpson
2020-02-07 12:14 ` Richard Henderson
2020-02-07 12:43 ` Taylor Simpson
2020-02-07 15:49 ` Richard Henderson
2020-02-09 5:08 ` Taylor Simpson
2020-02-09 18:17 ` Richard Henderson
2020-02-09 20:51 ` Taylor Simpson
2020-02-10 4:54 ` Taylor Simpson
2020-02-10 16:33 ` Richard Henderson
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=858bff3f-6e24-20a7-a7f3-49bee2cb8e12@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=tsimpson@quicinc.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).