From: Greg Kurz <groug@kaod.org>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v2] qtest: ask endianness of the target in qtest_init()
Date: Fri, 7 Oct 2016 15:08:46 +0200 [thread overview]
Message-ID: <20161007150846.2041fab1@bahia> (raw)
In-Reply-To: <09992696-731a-248b-bf59-ed95087c0256@redhat.com>
On Fri, 7 Oct 2016 14:56:26 +0200
Laurent Vivier <lvivier@redhat.com> wrote:
> On 07/10/2016 14:52, Peter Maydell wrote:
> > On 7 October 2016 at 13:45, Greg Kurz <groug@kaod.org> wrote:
> >> On Fri, 7 Oct 2016 13:31:10 +0100
> >> Peter Maydell <peter.maydell@linaro.org> wrote:
> >>
> >>> On 7 October 2016 at 13:27, Greg Kurz <groug@kaod.org> wrote:
> >>>> Indeed but my suggestion is to open code this in qvirtio_is_big_endian(),
> >>>> and even rename QTestState::big_endian to virtio_big_endian to make it
> >>>> really obvious it should not be used elsewhere.
> >>>>
> >>>> I now remember this is what I was resolutely suggested to do in
> >>>> include/qom/cpu.h at the time we started to support ppc64le:
> >>>>
> >>>> bool (*virtio_is_big_endian)(CPUState *cpu);
> >>>
> >>> Not really the same thing though -- virtio_is_big_endian
> >>> in QEMU is indeed used only in virtio, because it makes
> >>> dubious use of the internals of the CPU state. The
> >>> equivalent of this proposed qtest function is the #define
> >>> TARGET_BIG_ENDIAN, which is global to all of QEMU and
> >>> reasonably widely used (because it's not a property of
> >>> the CPU's internals).
> >>>
> >>
> >> Indeed but is it expected to be used in other tests than
> >> virtio ?
> >
> > Well, that's where we came in.
> >
> > Personally I'd rather see this patch purely fix the current
> > rather dodgy implementation of the existing qtest_big_endian()
> > function, which seems to be non-controversial, rather than
> > getting bogged down too much in the questions about what the
> > function name should be and how widely it should be used, etc.
>
> I'd rather too..
>
Fair enough.
> And I can rework this part later, as I've a series to enable virtio
> tests for SPAPR.
>
> So if v2 covers all non virtio naming space issues, is it acceptable as-is?
>
What I said with v1 still stands: this is an improvement over what we currently
have.
Reviewed-by: Greg Kurz <groug@kaod.org>
> Thanks,
> Laurent
Cheers.
--
Greg
next prev parent reply other threads:[~2016-10-07 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 10:14 [Qemu-devel] [PATCH v2] qtest: ask endianness of the target in qtest_init() Laurent Vivier
2016-10-07 10:48 ` Greg Kurz
2016-10-07 10:57 ` Laurent Vivier
2016-10-07 12:27 ` Greg Kurz
2016-10-07 12:31 ` Peter Maydell
2016-10-07 12:45 ` Greg Kurz
2016-10-07 12:52 ` Peter Maydell
2016-10-07 12:56 ` Laurent Vivier
2016-10-07 13:08 ` Greg Kurz [this message]
2016-10-10 4:55 ` David Gibson
2016-10-10 9:18 ` Peter Maydell
2016-10-10 13:39 ` David Gibson
2016-10-10 14:10 ` Peter Maydell
2016-10-11 1:24 ` David Gibson
2016-10-11 3:56 ` David Gibson
2016-10-11 8:55 ` Peter Maydell
2016-10-11 9:56 ` David Gibson
2016-10-10 4:52 ` David Gibson
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=20161007150846.2041fab1@bahia \
--to=groug@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@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 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.