From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: tony.nguyen@bt.com, Eduardo Habkost <ehabkost@redhat.com>,
Aleksandar Rikalo <arikalo@wavecomp.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
QEMU Developers <qemu-devel@nongnu.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Aleksandar Markovic <amarkovic@wavecomp.com>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 1/1] configure: Define target access alignment in configure
Date: Tue, 30 Jul 2019 22:14:15 +0200 [thread overview]
Message-ID: <CAL1e-=izLDXOQhFc1z84pEfBAr9SiQmSvN3-cSOawRMXP44oGw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-s6zEtZ73mBjw0S7r4+y=EJ=4jPqKX57rdTOeTvQCeRQ@mail.gmail.com>
On Tue, Jul 30, 2019 at 10:06 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> On Tue, 30 Jul 2019 at 21:00, Aleksandar Markovic
> <aleksandar.m.mail@gmail.com> wrote:
> >
> > On Thu, Jul 25, 2019 at 3:25 AM <tony.nguyen@bt.com> wrote:
> >
> > > Rename ALIGNED_ONLY to TARGET_ALIGNED_ONLY for clarity and move
> > > defines out of target/foo/cpu.h into configure, as we do with
> > > TARGET_WORDS_BIGENDIAN, so that it is always defined early.
> > >
> > > Also, poison the symbol in include/exec/poison.h to prevent use in
> > > common code.
> > >
> > >
> > Hi, Tony.
> >
> > Thanks for this new version.
> >
> > When one mentions "also" in the commit message, this is a kind of strong
> > indication that the patch should be split into two patches.
> >
> > So, could you please consider moving "poison" part into a separate patch?
>
> I think in this case the issue is more in the phrasing of the commit
> message rather than the patch composition. The patch is
> introducing TARGET_ALIGNED_ONLY as something defined
> by configure, and the correct status for that macro is "needs to
> be in poison.h"; having an intermediate state where the macro
> exists but isn't poisoned isn't really a logical split of the work.
> (The previous ALIGNED_ONLY didn't have so much need to be
> poisoned because it was defined in cpu.h and so the only way to
> expect to get it was by pulling in cpu.h.)
>
>
Yes, I would say the same now that I am looking at the change more
carefully.
But then, repeating what you said, something like "poisoning is needed"
(together with an explanation "why") should be in the commit message.
"Also" doesn't not fit well here.
Aleksandar
> thanks
> -- PMM
>
prev parent reply other threads:[~2019-07-30 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 1:24 [Qemu-devel] [PATCH v3 0/1] configure: Define target access alignment in configure tony.nguyen
2019-07-25 1:25 ` [Qemu-devel] [PATCH v3 1/1] " tony.nguyen
2019-07-30 19:59 ` Aleksandar Markovic
2019-07-30 20:06 ` Peter Maydell
2019-07-30 20:14 ` Aleksandar Markovic [this message]
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='CAL1e-=izLDXOQhFc1z84pEfBAr9SiQmSvN3-cSOawRMXP44oGw@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=ehabkost@redhat.com \
--cc=jcmvbkbc@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=tony.nguyen@bt.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).