From: Richard Henderson <rth@twiddle.net>
To: Pranith Kumar <bobby.prani@gmail.com>, "Emilio G. Cota" <cota@braap.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] compiler: define QEMU_CACHELINE_SIZE
Date: Tue, 6 Jun 2017 01:18:23 -0700 [thread overview]
Message-ID: <8a4bac1c-9c7e-5f60-ac1c-c5aced0f8dbc@twiddle.net> (raw)
In-Reply-To: <CAJhHMCDHLrU5NEuZGJqkVcJyQnXYsrdcYbNiNw4DAgiT=0R9pQ@mail.gmail.com>
On 06/05/2017 10:39 PM, Pranith Kumar wrote:
> Is there any reason not to use sysconf(_SC_LEVEL1_DCACHE_LINESIZE)?
That's an excellent idea. In fact... see reply to 3/3.
r~
next prev parent reply other threads:[~2017-06-06 8:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 22:49 [Qemu-devel] [PATCH v2 0/3] tcg: allocate TB structs preceding translated code Emilio G. Cota
2017-06-05 22:49 ` [Qemu-devel] [PATCH v2 1/3] compiler: define QEMU_CACHELINE_SIZE Emilio G. Cota
2017-06-06 5:39 ` Pranith Kumar
2017-06-06 8:18 ` Richard Henderson [this message]
2017-06-06 16:11 ` Emilio G. Cota
2017-06-06 17:39 ` Richard Henderson
2017-06-06 20:28 ` Geert Martin Ijewski
2017-06-06 21:38 ` Emilio G. Cota
2017-06-06 22:01 ` Geert Martin Ijewski
2017-06-05 22:49 ` [Qemu-devel] [PATCH v2 2/3] tests: use QEMU_CACHELINE_SIZE instead of hard-coding it Emilio G. Cota
2017-06-06 5:40 ` Pranith Kumar
2017-06-05 22:49 ` [Qemu-devel] [PATCH v2 3/3] tcg: allocate TB structs before the corresponding translated code Emilio G. Cota
2017-06-06 5:36 ` Pranith Kumar
2017-06-06 17:13 ` Emilio G. Cota
2017-06-06 8:24 ` Richard Henderson
2017-06-06 16:25 ` Emilio G. Cota
2017-06-06 17:02 ` Richard Henderson
2017-06-06 17:31 ` Emilio G. Cota
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=8a4bac1c-9c7e-5f60-ac1c-c5aced0f8dbc@twiddle.net \
--to=rth@twiddle.net \
--cc=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=cota@braap.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 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).