[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130129111235.23466333.yoshikawa_takuya_b1@lab.ntt.co.jp>
Date: Tue, 29 Jan 2013 11:12:35 +0900
From: Takuya Yoshikawa <yoshikawa_takuya_b1@....ntt.co.jp>
To: Alex Williamson <alex.williamson@...hat.com>
Cc: Takuya Yoshikawa <takuya.yoshikawa@...il.com>,
Gleb Natapov <gleb@...hat.com>,
Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] kvm: IOMMU read-only mapping support
On Mon, 28 Jan 2013 08:36:56 -0700
Alex Williamson <alex.williamson@...hat.com> wrote:
> On Mon, 2013-01-28 at 21:25 +0900, Takuya Yoshikawa wrote:
> > On Mon, 28 Jan 2013 12:59:03 +0200
> > Gleb Natapov <gleb@...hat.com> wrote:
> >
> > > > It sets spte based on the old value that means the readonly flag check
> > > > is missed. We need to call kvm_arch_flush_shadow_all under this case.
> > > Why not just disallow changing memory region KVM_MEM_READONLY flag
> > > without deleting the region?
> >
> > Sounds good.
> >
> > If you prefer, I can fold the required change into my patch.
>
> That would seem to make my patch 1/2 unnecessary. Thanks,
I've decided not to fold that change into my
KVM: set_memory_region: Identify the requested change explicitly
since this is a functional change, see v3 I posted today.
Since QEMU is not the only hypervisor using KVM, we should make the
change with a proper subject informing every user of the new restriction.
If the maintainers prefer to remove Alex's patch 1/2 first and then
rebase my v3 patch, I can do so.
Takuya
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists