From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 6/6] KVM: introduce readonly memslot
Date: Tue, 19 Jun 2012 10:14:29 +0800 [thread overview]
Message-ID: <4FDFE085.8040205@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FDEFEB8.9000001@redhat.com>
On 06/18/2012 06:11 PM, Avi Kivity wrote:
>> static int check_memory_region_flags(struct kvm_userspace_memory_region *mem)
>> {
>> - if (mem->flags & ~KVM_MEM_LOG_DIRTY_PAGES)
>> + if (mem->flags & ~(KVM_MEM_LOG_DIRTY_PAGES | KVM_MEM_READONLY))
>> return -EINVAL;
>
> Only x86 supports readonly so far.
>
Right, will fix.
>>
>> -static unsigned long gfn_to_hva_many(struct kvm_memory_slot *slot, gfn_t gfn,
>> - gfn_t *nr_pages)
>> +static unsigned long __gfn_to_hva_many(struct kvm_memory_slot *slot, gfn_t gfn,
>> + gfn_t *nr_pages, bool write)
>> {
>> - if (!slot || slot->flags & KVM_MEMSLOT_INVALID)
>> + if (!slot || slot->flags & KVM_MEMSLOT_INVALID ||
>> + ((slot->flags & KVM_MEM_READONLY) && write))
>> return bad_hva();
>>
>> if (nr_pages)
>> @@ -1045,6 +1046,12 @@ static unsigned long gfn_to_hva_many(struct kvm_memory_slot *slot, gfn_t gfn,
>> return gfn_to_hva_memslot(slot, gfn);
>> }
>>
>> +static unsigned long gfn_to_hva_many(struct kvm_memory_slot *slot, gfn_t gfn,
>> + gfn_t *nr_pages)
>> +{
>> + return __gfn_to_hva_many(slot, gfn, nr_pages, true);
>> +}
>
> We have dozens of translation functions: read/write guest virtual, guest
> physical (nested and non nested), host virtual, host physical,
> atomic/nonatomic, sync/async, with/without slot lookup, and probably a
> few more I forgot.
>
Yes, they make me confused me too.
> I think we should refactor this into a series of on-step translations:
>
> /*
> * Translate gva/len write access to a number of tlb entries
> * (due to cross-page splits) or a fault
> */
> gva_to_tlb(gva, len, ACCESS_WRITE, &translation);
> /*
> * Translate tlb entries to callbacks that do I/O (either directly
> * or through KVM_EXIT_MMIO, provided there is no exception pending
> */
> tlb_to_io(&translation, &iolist, IO_ATOMIC);
> /*
> * Initiate I/O (if no exception)
> */
> run_iolist(&iolist, data);
>
> struct gpa_scatterlist {
> unsigned nr_entries;
> struct {
> gpa_t gpa;
> unsigned len;
> } entry[2];
> struct x86_exception exception;
> };
>
> struct kvm_iolist {
> unsigned nr_entries;
> struct kvm_ioentry {
> struct kvm_memslot *slot; /* NULL for mmio */
> struct something *kernel_iodevice;
> gfn_t page_in_slot;
> unsigned offset_in_page;
> unsigned len;
> void (*iofunc)(struct kvm_ioentry *entry, void *data);
> } entry[2];
> struct x86_exception execption;
> };
>
> This is of course outside the scope of this patchset, just something to
> think about (and write opinions on).
I will think it more and try to do it based on you idea after this patchset,
thank you, Avi!
prev parent reply other threads:[~2012-06-19 2:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 2:47 [PATCH v3 1/6] KVM: fix missing check for memslot flags Xiao Guangrong
2012-06-12 2:47 ` [PATCH v3 2/6] KVM: hide KVM_MEMSLOT_INVALID from userspace Xiao Guangrong
2012-06-12 2:47 ` [PATCH v3 3/6] KVM: introduce gfn_to_pfn_memslot_atomic Xiao Guangrong
2012-06-12 2:48 ` [PATCH v3 4/6] KVM: pass slot to hva_to_pfn Xiao Guangrong
2012-06-18 10:15 ` Avi Kivity
2012-06-19 2:17 ` Xiao Guangrong
2012-06-12 2:48 ` [PATCH v3 5/6] KVM: introduce gfn_to_hva_read/kvm_read_hva/kvm_read_hva_atomic Xiao Guangrong
2012-06-18 10:16 ` Avi Kivity
2012-06-19 2:24 ` Xiao Guangrong
2012-06-12 2:49 ` [PATCH v3 6/6] KVM: introduce readonly memslot Xiao Guangrong
2012-06-16 2:11 ` Marcelo Tosatti
2012-06-18 3:11 ` Xiao Guangrong
2012-06-18 9:50 ` Avi Kivity
2012-06-18 20:25 ` Marcelo Tosatti
2012-06-19 7:20 ` Gleb Natapov
2012-06-19 8:11 ` Avi Kivity
2012-06-18 10:11 ` Avi Kivity
2012-06-19 2:14 ` Xiao Guangrong [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=4FDFE085.8040205@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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).