From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>, "Greg Kurz" <groug@kaod.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>
Cc: david@gibson.dropbear.id.au, harshpb@linux.ibm.com,
npiggin@gmail.com, pbonzini@redhat.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
ravi.bangoria@amd.com
Subject: Re: [PATCH v6] ppc: Enable 2nd DAWR support on p10
Date: Fri, 7 Jul 2023 21:40:11 +0530 [thread overview]
Message-ID: <c93ce2b0-98ce-0d65-b799-9b0e2a4d9ce0@linux.ibm.com> (raw)
In-Reply-To: <9c7ca859-f568-9487-0776-a6464edc69b4@kaod.org>
On 7/7/23 19:54, Cédric Le Goater wrote:
> On 7/7/23 13:59, Greg Kurz wrote:
>> Hi Daniel and Shiva !
>>
>> On Fri, 7 Jul 2023 08:09:47 -0300
>> Daniel Henrique Barboza <danielhb413@gmail.com> wrote:
>>
>>> This one was a buzzer shot.
>>>
>>
>> Indeed ! :-) I would have appreciated some more time to re-assess
>> my R-b tag on this 2 year old bug though ;-)
>
> We should drop that patch IMO and ask for a resend with more tests
> but that's a lot of work to build a PR :/
>
Hi Cedric,
I will be taking care of Greg's comment on avoiding failures in TCG mode for
cap-dawr1=on. I have already shared the "make test" results.
Do you want me to try any other tests?
Daniel, Apologies again for forcing you to rebuilding the PR.
Thanks,
Shivaprasad
<snip>
next prev parent reply other threads:[~2023-07-07 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 8:47 [PATCH v6] ppc: Enable 2nd DAWR support on p10 Shivaprasad G Bhat
2023-07-07 11:09 ` Daniel Henrique Barboza
2023-07-07 11:59 ` Greg Kurz
2023-07-07 12:22 ` Daniel Henrique Barboza
2023-07-07 16:01 ` Shivaprasad G Bhat
2023-07-08 6:25 ` Greg Kurz
2023-07-07 14:24 ` Cédric Le Goater
2023-07-07 14:49 ` Daniel Henrique Barboza
2023-07-07 16:10 ` Shivaprasad G Bhat [this message]
2023-07-08 1:24 ` Nicholas Piggin
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=c93ce2b0-98ce-0d65-b799-9b0e2a4d9ce0@linux.ibm.com \
--to=sbhat@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=ravi.bangoria@amd.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).