From: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>, qemu-devel@nongnu.org
Cc: mjrosato@linux.vnet.ibm.com, peter.maydell@linaro.org,
pasic@linux.vnet.ibm.com, alifm@linux.vnet.ibm.com,
eskultet@redhat.com, david@redhat.com, pmorel@linux.vnet.ibm.com,
cohuck@redhat.com, heiko.carstens@de.ibm.com,
alex.williamson@redhat.com, agraf@suse.de,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
jjherne@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
pbonzini@redhat.com, bjsdjshi@linux.vnet.ibm.com,
eric.auger@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v5 4/6] s390x/vfio: ap: Introduce VFIO AP device
Date: Mon, 14 May 2018 15:18:54 -0400 [thread overview]
Message-ID: <0dea8e93-703d-8237-864d-a64ce157cfe1@linux.vnet.ibm.com> (raw)
In-Reply-To: <59037385-06ae-e7e6-97a0-73b8acb4bee1@linux.ibm.com>
On 05/11/2018 06:29 AM, Halil Pasic wrote:
>
>
> On 05/10/2018 03:10 PM, Tony Krowiak wrote:
>>> If I did not. I think this is a big problem. We need to at least
>>> zeroize the queues (e.g. on system reset) to avoid leaking
>>> sensitive information. Without this, there is no sane way to use
>>> ap-passthrough. Or am I wrong?
>>
>> I do not have a definitive answer, I will have to look into it.
>> I'm thinking that since we are using ap-passthrough, the AP bus
>> running on the guest would be responsible for handling reset possibly
>> by resetting or zeroizing its queues. I'll get back to you on this.
>
> You are on the wrong track. What I'm talking about is the responsibility
> of the hypervisor and not the responsibility of the guest.
I think Pierre covered it in his reply.
>
>
> Regards,
> Halil
>
>
next prev parent reply other threads:[~2018-05-14 19:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:24 [Qemu-devel] [PATCH v5 0/6] s390x: vfio-ap: guest dedicated crypto adapters Tony Krowiak
2018-05-08 12:24 ` [Qemu-devel] [PATCH v5 1/6] linux-headers: linux header updates for AP support Tony Krowiak
2018-05-08 12:24 ` [Qemu-devel] [PATCH v5 2/6] s390x/ap: base Adjunct Processor (AP) object Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 3/6] s390x/cpumodel: Set up CPU model for AP device support Tony Krowiak
2018-05-15 12:00 ` Pierre Morel
2018-05-15 15:03 ` Tony Krowiak
2018-05-16 9:05 ` Pierre Morel
2018-05-16 9:23 ` David Hildenbrand
2018-05-16 10:41 ` Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 4/6] s390x/vfio: ap: Introduce VFIO AP device Tony Krowiak
2018-05-09 14:28 ` Halil Pasic
2018-05-10 13:10 ` Tony Krowiak
2018-05-11 9:02 ` Pierre Morel
2018-05-14 19:26 ` Tony Krowiak
2018-05-15 7:55 ` Pierre Morel
2018-05-15 15:09 ` Tony Krowiak
2018-05-16 9:09 ` Pierre Morel
2018-05-16 10:43 ` Tony Krowiak
2018-05-11 10:29 ` Halil Pasic
2018-05-14 19:18 ` Tony Krowiak [this message]
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 5/6] s390: doc: detailed specifications for AP virtualization Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 6/6] MAINTAINERS: add entries for AP Tony Krowiak
2018-05-08 12:46 ` Cornelia Huck
2018-05-08 12:47 ` Cornelia Huck
2018-05-09 13:29 ` Tony Krowiak
2018-05-08 13:47 ` Halil Pasic
2018-05-09 13:30 ` Tony Krowiak
2018-05-09 3:46 ` Alexey Kardashevskiy
2018-05-09 13:28 ` Tony Krowiak
2018-05-08 12:48 ` [Qemu-devel] [PATCH v5 0/6] s390x: vfio-ap: guest dedicated crypto adapters no-reply
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=0dea8e93-703d-8237-864d-a64ce157cfe1@linux.vnet.ibm.com \
--to=akrowiak@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eric.auger@redhat.com \
--cc=eskultet@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.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).