From: Wei Liu <wei.liu2@citrix.com>
To: Jason Dickens <jdickens@grammatech.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Adding new custom devices to Xen via QEMU
Date: Fri, 30 Sep 2016 12:33:45 +0100 [thread overview]
Message-ID: <20160930113345.GC2958@citrix.com> (raw)
In-Reply-To: <084ba422-9abe-de8a-8069-d6e62fd5a2d7@grammatech.com>
Hello
On Thu, Sep 29, 2016 at 09:35:21AM -0400, Jason Dickens wrote:
> Hello,
>
> My name is Jason Dickens and I'm a Research Scientist here at GrammaTech.
> Some of our research involves securing hypervisors and we have needed to add
> to and/or modify Xen. I have been successful in modifying the source for
> various purposes, but my question now is about devices. We have a custom
> device model implemented in QEMU which works great with QEMU (on Intel)
> standalone and with KVM, however, we now want access to it in Xen using the
> same modified QEMU build.
> The only problem I seem to be having is getting Xen to send the MMIO R/W's
> to QEMU. The device is being realized, but guest access to the physical
> address range I expect to reference the device seem to go no place. I see in
> the source calls such as "register_io_handler" that other devices use to
> effect the EPT mapping. Is this what I need?
> My main question is whether or not it is truly necessary to change Xen
> itself in order to introduce new devices in Xen using QEMU, or is there just
> a configuration setting? And what is the simplest way to have a range of
It is most likely achievable by just configuring your PCI device (?) in
QEMU (provided it has a reasonable BAR size or whatnot). Check out
various device model options in xl.cfg manpage, especially
device_model_args= option allows you to add arbitrary options to QEMU.
Wei.
> physical addresses access a custom QEMU device?
>
> Thanks,
> Jason
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-30 11:33 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 [this message]
2016-09-30 13:35 ` Jason Dickens
2016-09-30 13:53 ` David Vrabel
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=20160930113345.GC2958@citrix.com \
--to=wei.liu2@citrix.com \
--cc=jdickens@grammatech.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.