From: Bharata B Rao <bharata@linux.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, linuxram@us.ibm.com, qemu-devel@nongnu.org,
paulus@ozlabs.org
Subject: Re: [PATCH v1 ppc-for-5.0 2/2] ppc/spapr: Support reboot of secure pseries guest
Date: Thu, 12 Dec 2019 11:19:25 +0530 [thread overview]
Message-ID: <20191212054925.GA28362@in.ibm.com> (raw)
In-Reply-To: <20191211052742.GQ207300@umbus.fritz.box>
On Wed, Dec 11, 2019 at 04:27:42PM +1100, David Gibson wrote:
> Ah, right. We'll need to check for -ENOTTY specifically and ignore
> it, then. We don't want this spewing warnings on every non-secure
> guest.
I am posting v2 with explicit check for -ENOTTY.
>
> > It looks like we may need a new KVM capability to advertise the presence
> > of KVM_PPC_SVM_OFF ioctl (or more generally, to advertise host kernel's
> > capability to support secure guests).
>
> Actually, that's probably a better idea still.
If and when we decide to have this KVM capability and that goes upstream,
we can update the QEMU accordingly?
Regards,
Bharata.
prev parent reply other threads:[~2019-12-12 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 7:00 [PATCH v1 ppc-for-5.0 0/2] ppc/spapr: Support reboot of secure pseries guest Bharata B Rao
2019-12-09 7:00 ` [PATCH v1 ppc-for-5.0 1/2] linux-headers: Update Bharata B Rao
2019-12-09 7:00 ` [PATCH v1 ppc-for-5.0 2/2] ppc/spapr: Support reboot of secure pseries guest Bharata B Rao
2019-12-10 3:28 ` David Gibson
2019-12-10 3:50 ` Bharata B Rao
2019-12-10 4:03 ` Alexey Kardashevskiy
2019-12-10 5:05 ` David Gibson
2019-12-10 6:50 ` Bharata B Rao
2019-12-10 23:41 ` David Gibson
2019-12-11 5:08 ` Bharata B Rao
2019-12-11 5:27 ` David Gibson
2019-12-12 5:49 ` Bharata B Rao [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=20191212054925.GA28362@in.ibm.com \
--to=bharata@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=linuxram@us.ibm.com \
--cc=paulus@ozlabs.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 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.