From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57214) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YIyMD-0005HJ-Qx for qemu-devel@nongnu.org; Wed, 04 Feb 2015 06:42:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YIyM8-0006SM-MD for qemu-devel@nongnu.org; Wed, 04 Feb 2015 06:42:57 -0500 Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]:44195) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YIyM8-0006S8-Eu for qemu-devel@nongnu.org; Wed, 04 Feb 2015 06:42:52 -0500 Received: by mail-wi0-f176.google.com with SMTP id bs8so31200557wib.3 for ; Wed, 04 Feb 2015 03:42:51 -0800 (PST) Sender: Paolo Bonzini Message-ID: <54D205B7.7080109@redhat.com> Date: Wed, 04 Feb 2015 12:42:47 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1422965498-11500-1-git-send-email-thuth@linux.vnet.ibm.com> <1422965498-11500-2-git-send-email-thuth@linux.vnet.ibm.com> <54D0C76B.70603@redhat.com> <20150203161601.1319f7ef@oc7435384737.ibm.com> <54D0E7B8.2060501@redhat.com> <54D1D7A3.8010508@de.ibm.com> <54D1F6E2.1040201@redhat.com> <54D20190.9060201@de.ibm.com> In-Reply-To: <54D20190.9060201@de.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFC 1/1] KVM: s390: Add MEMOP ioctl for reading/writing guest memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christian Borntraeger , Thomas Huth Cc: cornelia.huck@de.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org, agraf@suse.de On 04/02/2015 12:25, Christian Borntraeger wrote: > Whenever vhost or qemu or a finished aio request wrote content into a > virtio buffer, the HW has set the storage key for that physical page, > which makes it automatically dirty/referenced in the guest visible > storage key. Ah, I knew the storage keys were per-physical page, but I wasn't sure if they were separate for the host and the guest. That's obvious now. Can we detect non-zero storage key in emulated zPCI requests, and fail the request somehow? Paolo