From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] privcmd: MMAPBATCH: Fix error handling/reporting
Date: Wed, 20 May 2009 14:13:33 -0700 [thread overview]
Message-ID: <4A14727D.5000803@goop.org> (raw)
In-Reply-To: <1242830730-3341-1-git-send-email-ian.campbell@citrix.com>
Ian Campbell wrote:
> On error IOCTL_PRIVCMD_MMAPBATCH is expected to set the top nibble of
> the effected MFN and return 0. Currently it leaves the MFN unmodified
> and returns the number of failures. Therefore:
>
> - reimplement remap_domain_mfn_range() using direct
> HYPERVISOR_mmu_update() calls and small batches. The xen_set_domain_pte()
> interface does not report errors and since some failures are
> expected/normal using the multicall infrastructure is too noisy.
> - return 0 as expected
> - writeback the updated MFN list to mmapbatch->arr not over mmapbatch,
> smashing the caller's stack.
> - remap_domain_mfn_range can be static.
>
> With this change I am able to start an HVM domain.
>
This breaks compiling xenfs as a module; neither flush_tlb_all or
arbitrary_virt_to_machine are exported, I think.
J
next prev parent reply other threads:[~2009-05-20 21:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 14:44 [GIT] privcmd fixes --> working HVM Ian Campbell
2009-05-20 14:45 ` [PATCH] privcmd: MMAPBATCH: Fix error handling/reporting Ian Campbell
2009-05-20 19:33 ` Jeremy Fitzhardinge
2009-05-21 8:51 ` Ian Campbell
2009-05-21 9:18 ` Ian Campbell
2009-05-21 9:18 ` [PATCH] xen/privcmd: move remap_domain_mfn_range() to core xen code and export Ian Campbell
2009-05-21 9:19 ` Ian Campbell
2009-05-21 17:14 ` [PATCH] privcmd: MMAPBATCH: Fix error handling/reporting Jeremy Fitzhardinge
2009-05-20 21:13 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 19:22 Boris Derzhavets
2009-05-21 8:09 Boris Derzhavets
2009-05-21 17:16 ` Jeremy Fitzhardinge
2009-05-22 18:07 Boris Derzhavets
2009-05-22 18:22 ` Pasi Kärkkäinen
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=4A14727D.5000803@goop.org \
--to=jeremy@goop.org \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.