From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH RFC 1/1] KVM: s390: Add MEMOP ioctl for reading/writing guest memory Date: Wed, 04 Feb 2015 12:42:47 +0100 Message-ID: <54D205B7.7080109@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: cornelia.huck@de.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org, agraf@suse.de To: Christian Borntraeger , Thomas Huth Return-path: Received: from mail-we0-f181.google.com ([74.125.82.181]:44069 "EHLO mail-we0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932433AbbBDLmw (ORCPT ); Wed, 4 Feb 2015 06:42:52 -0500 Received: by mail-we0-f181.google.com with SMTP id k48so1179755wev.12 for ; Wed, 04 Feb 2015 03:42:51 -0800 (PST) In-Reply-To: <54D20190.9060201@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: 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