From: David Vrabel <david.vrabel@citrix.com>
To: Jason Dickens <jdickens@grammatech.com>, Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Adding new custom devices to Xen via QEMU
Date: Fri, 30 Sep 2016 14:53:57 +0100 [thread overview]
Message-ID: <57EE6E75.4090109@citrix.com> (raw)
In-Reply-To: <41099728-5681-81e8-6892-82192551deaf@grammatech.com>
On 30/09/16 14:35, Jason Dickens wrote:
> Hi Wei,
>
> Thanks for the response. It make sense to me that if the device were on
> the PCI bus (or other such bus, e.g. USB) that it could be discovered,
> at least by an OS. Its something to consider. I should mention that our
> guest VM doesn't actually use an OS.
>
> However, the device is not implemented that as PCI it is simply memory
> mapped. Technically, in QEMU is has type ISA because it was derived as a
> modification of the TPM device. Is it possible something is lacking in
> the QEMU model that Xen needs but KVM doesn't?
> If the answer is that Xen should not need modification for any new
> devices then this gives me hope. You've also inspired some things to
> try, like whether or not smaller modifications to the TPM device work.
> One change that is significant to mention is that the physical address
> range use is anomalous, by which I mean it not in the normal device range.
Does device MMIO overlap with guest RAM? If so, you'll need to
unpopulate the RAM first.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-30 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 13:35 Adding new custom devices to Xen via QEMU Jason Dickens
2016-09-30 11:33 ` Wei Liu
2016-09-30 13:35 ` Jason Dickens
2016-09-30 13:53 ` David Vrabel [this message]
2016-09-30 14:29 ` Jason Dickens
2016-09-30 18:42 ` Konrad Rzeszutek Wilk
[not found] ` <b980347d-d77b-d33e-4de9-8ed2f042c136@grammatech.com>
2016-09-30 19:47 ` Konrad Rzeszutek Wilk
2016-09-30 20:06 ` Jason Dickens
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=57EE6E75.4090109@citrix.com \
--to=david.vrabel@citrix.com \
--cc=jdickens@grammatech.com \
--cc=wei.liu2@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 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.