From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: Keir Fraser <keir@xen.org>, xen-devel@lists.xen.org
Subject: Re: [PATCH RFC] ioreq-server: handle the lack of a default emulator properly
Date: Fri, 26 Sep 2014 17:23:19 +0100 [thread overview]
Message-ID: <5425AF170200007800039DF0@mail.emea.novell.com> (raw)
In-Reply-To: <1411745473-5075-1-git-send-email-paul.durrant@citrix.com>
>>> On 26.09.14 at 17:31, <paul.durrant@citrix.com> wrote:
> This fix should probably go in 4.5 but this patch is RFC for the moment
> because of uncertainty about what to do for unemulated MMIO accesses.
> Originally I forced a domain crash in this case, but hvmloader actually
> hit the crash because the code that deals with building the ACPI TPM
> info reads from 0xFED40F00 looking for a signature value and there is
> nothing backing this access in my configuration. So, the question is
> whether to whitelist this access in some way or make building that
> table optional in some way so that it is only invoked if an emulated
> TPM is definitely present.
I think in the sense of acting like real hardware, having a definite
point to complete such I/O is quite desirable, as opposed to killing
the guest.
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -2386,8 +2386,7 @@ static struct hvm_ioreq_server *hvm_select_ioreq_server(struct domain *d,
> if ( list_empty(&d->arch.hvm_domain.ioreq_server.list) )
> return NULL;
>
> - if ( list_is_singular(&d->arch.hvm_domain.ioreq_server.list) ||
> - (p->type != IOREQ_TYPE_COPY && p->type != IOREQ_TYPE_PIO) )
> + if ( p->type != IOREQ_TYPE_COPY && p->type != IOREQ_TYPE_PIO )
I'm having some trouble understanding the reason for this change.
Jan
next prev parent reply other threads:[~2014-09-26 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:31 [PATCH RFC] ioreq-server: handle the lack of a default emulator properly Paul Durrant
2014-09-26 16:23 ` Jan Beulich [this message]
2014-09-29 8:59 ` Paul Durrant
2014-09-29 9:28 ` Jan Beulich
2014-09-29 9:33 ` Paul Durrant
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=5425AF170200007800039DF0@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).