Displaying 20 results from an estimated 20000 matches similar to: "PARAVIRT_SAVE_FLAGS_IRQ_DISABLE composite callsite"
2015 Nov 03
1
[RFC PATCH] x86/paravirt: Kill some unused patching functions
From: Borislav Petkov <bp at suse.de>
paravirt_patch_ignore() is completely unused and paravirt_patch_nop()
doesn't do a whole lot. Remove them both.
Signed-off-by: Borislav Petkov <bp at suse.de>
Cc: Andrew Morton <akpm at linux-foundation.org>
Cc: Andy Lutomirski <luto at kernel.org>
Cc: Chris Wright <chrisw at sous-sol.org>
Cc: "H. Peter Anvin"
2015 Nov 03
1
[RFC PATCH] x86/paravirt: Kill some unused patching functions
From: Borislav Petkov <bp at suse.de>
paravirt_patch_ignore() is completely unused and paravirt_patch_nop()
doesn't do a whole lot. Remove them both.
Signed-off-by: Borislav Petkov <bp at suse.de>
Cc: Andrew Morton <akpm at linux-foundation.org>
Cc: Andy Lutomirski <luto at kernel.org>
Cc: Chris Wright <chrisw at sous-sol.org>
Cc: "H. Peter Anvin"
2008 Jul 07
10
[PATCH RFC 0/4] Paravirtual spinlocks
At the most recent Xen Summit, Thomas Friebel presented a paper
("Preventing Guests from Spinning Around",
http://xen.org/files/xensummitboston08/LHP.pdf) investigating the
interactions between spinlocks and virtual machines. Specifically, he
looked at what happens when a lock-holding VCPU gets involuntarily
preempted.
The obvious first order effect is that while the VCPU is not
2008 Jul 07
10
[PATCH RFC 0/4] Paravirtual spinlocks
At the most recent Xen Summit, Thomas Friebel presented a paper
("Preventing Guests from Spinning Around",
http://xen.org/files/xensummitboston08/LHP.pdf) investigating the
interactions between spinlocks and virtual machines. Specifically, he
looked at what happens when a lock-holding VCPU gets involuntarily
preempted.
The obvious first order effect is that while the VCPU is not
2008 Jul 07
10
[PATCH RFC 0/4] Paravirtual spinlocks
At the most recent Xen Summit, Thomas Friebel presented a paper
("Preventing Guests from Spinning Around",
http://xen.org/files/xensummitboston08/LHP.pdf) investigating the
interactions between spinlocks and virtual machines. Specifically, he
looked at what happens when a lock-holding VCPU gets involuntarily
preempted.
The obvious first order effect is that while the VCPU is not
2010 Jul 28
23
HVM hypercalls
Hi
I need to use hypercalls from HVM domain (e.g. HYPERVISOR_add_to_physmap). However, it does not work when I am trying to invoke it from HVM Linux guest. Basically, I don''t see that anything happens on hypervisor''s side. I also grep''ed the guest code for ''vmmcall''/''vmcall'' and did not find anything. Is it possible to do it at all?
2013 Feb 25
9
[PATCH] MAINTAINERS: Provide proper URL to the upstream Linux development tree for Xen.
And also put my name behind the mainternship.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0358a3e..e2252fc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -193,8 +193,9 @@ F: xen/include/xen/iommu.h
LINUX (PV_OPS)
M: Jeremy Fitzhardinge
2007 Apr 18
23
[patch 00/20] paravirt_ops updates
Hi Andi,
Here's a repost of the paravirt_ops update series I posted the other day.
Since then, I found a few potential bugs with patching clobbering,
cleaned up and documented paravirt.h and the patching machinery.
Overview:
add-MAINTAINERS.patch
obvious
remove-CONFIG_DEBUG_PARAVIRT.patch
No longer meaningful or needed.
paravirt-nop.patch
Clean up nop paravirt_ops functions, mainly to
2007 Apr 18
23
[patch 00/20] paravirt_ops updates
Hi Andi,
Here's a repost of the paravirt_ops update series I posted the other day.
Since then, I found a few potential bugs with patching clobbering,
cleaned up and documented paravirt.h and the patching machinery.
Overview:
add-MAINTAINERS.patch
obvious
remove-CONFIG_DEBUG_PARAVIRT.patch
No longer meaningful or needed.
paravirt-nop.patch
Clean up nop paravirt_ops functions, mainly to
2009 Mar 03
11
Fw: Re: Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium
>I probably shouldn''t have been operating machinery yesterday.
>The crash is probably because I committed the e820 memory rearranging
>stuff into the wrong branch, but something may have broken us from
>tip/master as well.
> J
Kernel was already broken at 2/28/09
--- On Sat, 2/28/09, Marc - A. Dahlhaus <mad@wol.de> wrote:
From: Marc - A. Dahlhaus
2010 Oct 26
4
[PATCH] x86/pvclock-xen: zero last_value on resume
If the guest domain has been suspend/resumed or migrated, then the
system clock backing the pvclock clocksource may revert to a smaller
value (ie, can be non-monotonic across the migration/save-restore).
Make sure we zero last_value in that case so that the domain
continues to see clock updates.
[ I don't know if kvm needs an analogous fix or not. ]
Signed-off-by: Jeremy Fitzhardinge
2010 Oct 26
4
[PATCH] x86/pvclock-xen: zero last_value on resume
If the guest domain has been suspend/resumed or migrated, then the
system clock backing the pvclock clocksource may revert to a smaller
value (ie, can be non-monotonic across the migration/save-restore).
Make sure we zero last_value in that case so that the domain
continues to see clock updates.
[ I don't know if kvm needs an analogous fix or not. ]
Signed-off-by: Jeremy Fitzhardinge
2010 Oct 26
4
[PATCH] x86/pvclock-xen: zero last_value on resume
If the guest domain has been suspend/resumed or migrated, then the
system clock backing the pvclock clocksource may revert to a smaller
value (ie, can be non-monotonic across the migration/save-restore).
Make sure we zero last_value in that case so that the domain
continues to see clock updates.
[ I don't know if kvm needs an analogous fix or not. ]
Signed-off-by: Jeremy Fitzhardinge
2010 Jun 25
6
Dom0 reboot when several VM reboot at the same time
Hi folks,
I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0
reboot it self:
Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update
and reboot itself every 3:00 AM.
# last
... ...
admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50)
reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3)
admin pts/0
2010 Jun 25
6
Dom0 reboot when several VM reboot at the same time
Hi folks,
I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0
reboot it self:
Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update
and reboot itself every 3:00 AM.
# last
... ...
admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50)
reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3)
admin pts/0
2009 May 07
1
[PATCH 5/5] xen: reserve Xen start_info rather than e820 reserving
Use reserve_early rather than e820 reservations for Xen start info and mfn->pfn
table, so that the memory use is a bit more self-documenting.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
---
arch/x86/xen/setup.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 15c6c68..ad0047f 100644
2007 Apr 18
17
[patch 00/17] paravirt_ops updates
Hi Andi,
This series of patches updates paravirt_ops in various ways. Some of the
changes are plain cleanups and improvements, and some add some interfaces
necessary for Xen.
The brief overview:
add-MAINTAINERS.patch - obvious
remove-CONFIG_DEBUG_PARAVIRT.patch - no longer needed
paravirt-nop.patch - mark nop operations consistently
paravirt-pte-accessors.patch - operations to pack/unpack
2007 Apr 18
17
[patch 00/17] paravirt_ops updates
Hi Andi,
This series of patches updates paravirt_ops in various ways. Some of the
changes are plain cleanups and improvements, and some add some interfaces
necessary for Xen.
The brief overview:
add-MAINTAINERS.patch - obvious
remove-CONFIG_DEBUG_PARAVIRT.patch - no longer needed
paravirt-nop.patch - mark nop operations consistently
paravirt-pte-accessors.patch - operations to pack/unpack
2007 Apr 18
3
What do we need to do to hit 2.6.19?
Chris said, and I agree, that we should try to get the basic PV-ops
infrastructure stuff into 2.6.19. To me this means being able to run a
kernel native with CONFIG_PARAVIRT, and see little or no functional or
performance degradation. What do we need to do to get there:
* fix the slowdown bug, which seems to be something to do with
rdmsr/wrmsr on SMP systems
* work out how to
2007 Apr 18
4
paravirt repo rebased to 2.6.21-rc6-mm1
Seems to work OK for native and Xen. I had to play a bit with the
paravirt-sched-clock patch to deal with the VMI changes. Zach, can you
check that it still works?
Thanks,
J