From: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Satheesh Rajendran" <sathnaga@linux.vnet.ibm.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] spapr: Print out extra hints when CAS negotiation of interrupt mode fails
Date: Thu, 16 May 2019 14:14:54 +0530 [thread overview]
Message-ID: <20190516084454.GC25414@sathnaga86> (raw)
In-Reply-To: <20190516103215.6ba7a70c@bahia.lan>
On Thu, May 16, 2019 at 10:32:15AM +0200, Greg Kurz wrote:
> On Thu, 16 May 2019 10:22:26 +0200
> Cédric Le Goater <clg@kaod.org> wrote:
>
> > On 5/16/19 9:45 AM, Satheesh Rajendran wrote:
> > > On Thu, May 16, 2019 at 09:36:57AM +0200, Greg Kurz wrote:
> > >> Let's suggest to the user how the machine should be configured to allow
> > >> the guest to boot successfully.
> > >>
> > >> Suggested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> > >> Signed-off-by: Greg Kurz <groug@kaod.org>
> > >> ---
> > >> hw/ppc/spapr_hcall.c | 4 ++--
> > >> 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > Reviewed-and-Tested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Reviewed-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Tested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Done!
> >
> > you should use two different tags. I don't think patchwork understand
> > compounds.
> >
> > C.
> >
>
Thanks !!
> It doesn't indeed.
>
> $ pwclient view 1100396 | grep Reviewed
> $
>
Regards,
-Satheesh.
> > > 2019-05-16T07:42:43.018771Z qemu-system-ppc64: Guest requested unavailable interrupt mode (XICS), either don't set the ic-mode machine property or try ic-mode=xics or ic-mode=dual
> > > 2019-05-16 07:42:43.394+0000: shutting down, reason=crashed
> > >
> > >>
> > >> diff --git a/hw/ppc/spapr_hcall.c b/hw/ppc/spapr_hcall.c
> > >> index 63a55614b83d..aae9fd2b3e6d 100644
> > >> --- a/hw/ppc/spapr_hcall.c
> > >> +++ b/hw/ppc/spapr_hcall.c
> > >> @@ -1646,12 +1646,12 @@ static target_ulong h_client_architecture_support(PowerPCCPU *cpu,
> > >> */
> > >> if (guest_xive) {
> > >> if (spapr->irq->ov5 == SPAPR_OV5_XIVE_LEGACY) {
> > >> - error_report("Guest requested unavailable interrupt mode (XIVE)");
> > >> + error_report("Guest requested unavailable interrupt mode (XIVE), try the ic-mode=xive or ic-mode=dual machine property");
> > >> exit(EXIT_FAILURE);
> > >> }
> > >> } else {
> > >> if (spapr->irq->ov5 == SPAPR_OV5_XIVE_EXPLOIT) {
> > >> - error_report("Guest requested unavailable interrupt mode (XICS)");
> > >> + error_report("Guest requested unavailable interrupt mode (XICS), either don't set the ic-mode machine property or try ic-mode=xics or ic-mode=dual");
> > >> exit(EXIT_FAILURE);
> > >> }
> > >> }
> > >>
> > >
> >
>
next prev parent reply other threads:[~2019-05-16 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 7:36 [Qemu-devel] [PATCH] spapr: Print out extra hints when CAS negotiation of interrupt mode fails Greg Kurz
2019-05-16 7:45 ` Satheesh Rajendran
2019-05-16 8:22 ` Cédric Le Goater
2019-05-16 8:32 ` Greg Kurz
2019-05-16 8:44 ` Satheesh Rajendran [this message]
2019-05-20 6:21 ` 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=20190516084454.GC25414@sathnaga86 \
--to=sathnaga@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).