Displaying 3 results from an estimated 3 matches for "68cc3c514a0a".
2012 Feb 14
1
[PATCH] x86: don't allow Dom0 to map MSI-X table writably
...with the upstream qemu tree not
being capable of handling passthrough, yet, there''s no need to treat
Dom specially here anymore.
This continues to leave unaddressed the case where PV guests map the
MSI-X table page(s) before setting up the first MSI-X interrupt (see
the original c/s 22182:68cc3c514a0a description for options).
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/arch/x86/mm.c
+++ b/xen/arch/x86/mm.c
@@ -869,7 +869,7 @@ get_page_from_l1e(
return -EINVAL;
}
- if ( !(l1f & _PAGE_RW) || IS_PRIV(pg_owner) ||
+ if ( !(l1f & _PA...
2010 Oct 08
17
MSI badness in xen-unstable
Hi,
I''ve been trying to boot stefano''s minimal dom0 kernel from
git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git
2.6.36-rc1-initial-domain-v2+pat
On xen-unstable, I get the following WARN_ON()''s from Xen when bringing
up the NIC''s, then the machine hangs forever when trying to login either
over serial or NIC.
(XEN) Xen WARN at msi.c:649
(XEN) ----[
2012 Jan 04
98
RFC: Still TODO for 4.2?
What are the outstanding things to do before we think we can start on
the 4.2 -rc''s? Does anyone have a timetable in mind?
hypervisor:
* ??? - Keir, Tim, Jan?
tools:
* libxl stable API -- we would like 4.2 to define a stable API
which downstream''s can start to rely on not changing. Aspects of
this are:
* event handling (IanJ working