From: "Alex Bennée" <alex.bennee@linaro.org>
To: luigi burdo <intermediadc@hotmail.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"programmingkidx@gmail.com" <programmingkidx@gmail.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"bharata@linux.vnet.ibm.com" <bharata@linux.vnet.ibm.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 0/3] Enable MTTCG on PPC64
Date: Sun, 09 Apr 2017 15:27:29 +0100 [thread overview]
Message-ID: <871st1wt9q.fsf@linaro.org> (raw)
In-Reply-To: <AM5P194MB01292723DDB978AC78F8FDD7C80E0@AM5P194MB0129.EURP194.PROD.OUTLOOK.COM>
luigi burdo <intermediadc@hotmail.com> writes:
> Hi David and Nikuji,
>
> can i suggest to remove the message:
>
>
> Guest not yet converted to MTTCG - you may get unexpected results
> where the mttcg is enabled?
Have you declared the memory ordering for the guest?
>
> another thing im finding is this message
> Guest expects a stronger memory ordering than the host provides
> This may cause strange/hard to debug errors
See ca759f9e387db87e1719911f019bc60c74be9ed8 for an example.
>
>
> I have 8 gb on my machine and this message come if i gave 512mb on the guest too.
>
> Is possible know where the mttcg is already enabled?
>
> i see on x86,i386,arm too if i set thread=multy the qemu start using the other host cores is on this guest system enabled?
>
> if yes i have the same messages of ppc64 too :
>
> Guest not yet converted to MTTCG - you may get unexpected results
>
> and
>
> Guest expects a stronger memory ordering than the host provides
> This may cause strange/hard to debug errors
>
>
> Ciao
>
> Luigi
>
>
> Applied to ppc-for-2.10. Anyone object to that for 2/3, which isn't
> within ppc code?
--
Alex Bennée
next prev parent reply other threads:[~2017-04-09 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 6:07 [Qemu-devel] [PATCH v2 0/3] Enable MTTCG on PPC64 Nikunj A Dadhania
2017-04-07 6:07 ` [Qemu-devel] [PATCH v2 1/3] target/ppc: Emulate LL/SC using cmpxchg helpers Nikunj A Dadhania
2017-04-07 18:26 ` Richard Henderson
2017-04-07 6:07 ` [Qemu-devel] [PATCH v2 2/3] cputlb: handle first atomic write to the page Nikunj A Dadhania
2017-04-07 6:07 ` [Qemu-devel] [PATCH v2 3/3] target/ppc: Generate fence operations Nikunj A Dadhania
2017-04-07 18:27 ` Richard Henderson
2017-04-07 17:49 ` [Qemu-devel] [Qemu-ppc] [PATCH v2 0/3] Enable MTTCG on PPC64 luigi burdo
2017-04-07 19:29 ` G 3
2017-04-07 20:11 ` luigi burdo
2017-04-08 11:16 ` luigi burdo
2017-04-09 14:17 ` Alex Bennée
2017-04-08 6:51 ` [Qemu-devel] " David Gibson
2017-04-09 8:41 ` [Qemu-devel] [Qemu-ppc] " luigi burdo
2017-04-09 14:27 ` Alex Bennée [this message]
2017-04-09 17:10 ` luigi burdo
2017-04-10 5:43 ` Nikunj A Dadhania
2017-04-10 7:12 ` Alex Bennée
2017-04-10 7:47 ` Nikunj A Dadhania
2017-04-09 17:00 ` [Qemu-devel] " 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=871st1wt9q.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=intermediadc@hotmail.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).