On 11/18/10 01:41, Hidetoshi Seto wrote:
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
hw/virtio-9p-local.c:479: warning: implicit declaration of
Clear the vapic address immediately after reset. This allows dual-boot guests
to work efficiently, and more importantly, works around the bios using
'rep insb' to read in the option rom and confusing the vapic machinery.
Signed-off-by: Avi Kivity a...@redhat.com
---
target-i386/kvm.c | 12
(2010/11/18 14:45), Zachary Amsden wrote:
No, I believe your patch is correct and the lock should be there. Did you test
with spinlock debugging just to be sure?
Sorry but no.
I have no experience with cpu hotplug.
So I thought it would take too much time to do real test by myself and
Hello,
Am Donnerstag 18 November 2010 01:41:39 schrieb Hidetoshi Seto:
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
+#ifdef CONFIG_UTIMENSAT
+return utimensat(dirfd, path, times, flags);
(2010/11/18 17:02), Jes Sorensen wrote:
On 11/18/10 01:41, Hidetoshi Seto wrote:
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
On Thu, Nov 18, 2010 at 12:12:54AM +0200, Michael S. Tsirkin wrote:
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly without bouncing out to
a kernel thread.
While we touch this structure, rearrange irqfd fields to make fastpath
better packed for
(2010/11/18 17:28), Philipp Hahn wrote:
Hello,
Am Donnerstag 18 November 2010 01:41:39 schrieb Hidetoshi Seto:
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
+#ifdef CONFIG_UTIMENSAT
+return
On 11/18/10 09:48, Hidetoshi Seto wrote:
(2010/11/18 17:02), Jes Sorensen wrote:
Hi Hidetoshi,
I think the idea of the patch is good, but please move qemu_utimensat()
to oslib-posix.c and provide a wrapper for oslib-win32.c. It is
emulation for a system library function, so it doesn't belong
On Thu, Nov 18, 2010 at 11:05:22AM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 12:12:54AM +0200, Michael S. Tsirkin wrote:
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly without bouncing out to
a kernel thread.
While we touch this
Le jeudi 18 novembre 2010 à 07:28 +0100, Nikola Ciprich a écrit :
Yep, this is a known problem, thanks !
fix is there :
http://patchwork.ozlabs.org/patch/71354/
Thanks Eric, this indeed fixes the problem..
I noticed the fix didn't make it to 2.6.37-rc2-git3 though,
maybe it just
On Thu, Nov 18, 2010 at 11:16:02AM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 11:05:22AM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 12:12:54AM +0200, Michael S. Tsirkin wrote:
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly
On 11/18/2010 03:58 AM, Sheng Yang wrote:
On Wednesday 17 November 2010 21:58:00 Avi Kivity wrote:
On 11/15/2010 11:15 AM, Sheng Yang wrote:
This patch enable per-vector mask for assigned devices using MSI-X.
This patch provided two new APIs: one is for guest to specific device's
On 11/18/2010 04:22 AM, Sheng Yang wrote:
On Wednesday 17 November 2010 22:01:41 Avi Kivity wrote:
On 11/15/2010 11:15 AM, Sheng Yang wrote:
We need to query the entry later.
+int kvm_get_irq_routing_entry(struct kvm *kvm, int gsi,
+ struct kvm_kernel_irq_routing_entry
On 11/18/2010 09:17 AM, Xiao Guangrong wrote:
On 11/18/2010 01:36 AM, Marcelo Tosatti wrote:
I don't think we need to flush immediately; set a tlb dirty bit
somewhere that is cleareded when we flush the tlb.
kvm_mmu_notifier_invalidate_page() can consult the bit and force a
flush if
On Thu, Nov 18, 2010 at 11:05:22AM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 12:12:54AM +0200, Michael S. Tsirkin wrote:
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly without bouncing out to
a kernel thread.
While we touch this
On Thu, Nov 18, 2010 at 11:28:02AM +0200, Avi Kivity wrote:
On 11/18/2010 03:58 AM, Sheng Yang wrote:
On Wednesday 17 November 2010 21:58:00 Avi Kivity wrote:
On 11/15/2010 11:15 AM, Sheng Yang wrote:
This patch enable per-vector mask for assigned devices using MSI-X.
This patch
On Thu, Nov 18, 2010 at 11:30:47AM +0200, Avi Kivity wrote:
*entry may be stale after rcu_read_unlock(). Is this a problem?
I suppose not. All MSI-X MMIO accessing would be executed without delay, so
no re-
order issue would happen. If the guest is reading and writing the field at
On Wed, Nov 17, 2010 at 09:29:22AM +0800, Sheng Yang wrote:
+#define KVM_MSIX_TYPE_ASSIGNED_DEV 1
+
+#define KVM_MSIX_FLAG_MASKBIT(1 0)
+#define KVM_MSIX_FLAG_QUERY_MASKBIT (1 0)
+
+struct kvm_msix_entry {
+ __u32 id;
+ __u32 type;
Is type
On 11/18/2010 12:12 AM, Michael S. Tsirkin wrote:
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly without bouncing out to
a kernel thread.
While we touch this structure, rearrange irqfd fields to make fastpath
better packed for better cache utilization.
On 11/01/2010 10:14 AM, Alex Williamson wrote:
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamsonalex.william...@redhat.com
---
hw/pc.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 69b13bf..0ea6d10
On Thu, Nov 18, 2010 at 11:34:26AM +0200, Michael S. Tsirkin wrote:
@@ -125,10 +129,18 @@ irqfd_wakeup(wait_queue_t *wait, unsigned mode, int
sync, void *key)
{
struct _irqfd *irqfd = container_of(wait, struct _irqfd, wait);
unsigned long flags = (unsigned long)key;
+
On Wed, Nov 17, 2010 at 09:54:27PM +, Blue Swirl wrote:
2010/11/16 Gleb Natapov g...@redhat.com:
On Tue, Nov 16, 2010 at 06:30:19PM +, Blue Swirl wrote:
Perhaps the FW path should use device class names if no name is
specified.
What do you mean by device class name. We can do
Bugs item #1841658, was opened at 2007-11-30 13:11
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1841658group_id=180599
Please note that this message will contain a full copy of the comment
Reviewed-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 11/18/2010 12:58 AM, Kenni Lund wrote:
Hi
I'm about to move a couple of virtual machines from a Fedora 11 system
to a new server with a more recent operating system and newer version
of KVM, etc.
One of the guests is a Windows Server 2003 Standard SP2, which is
currently running with the
So the following on top will fix it all.
Any more comments befpre I bundle it up,
test and report?
kvm: fix up msi fastpath
This will be folded into the msi fastpath patch.
Changes:
- simplify irq_entry/irq_routing update rules:
simply to it all under irqfds.lock
- document locking for rcu
Bugs item #1998355, was opened at 2008-06-20 02:11
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1998355group_id=180599
Please note that this message will contain a full copy of the comment
On 11/18/2010 12:57 PM, Michael S. Tsirkin wrote:
So the following on top will fix it all.
Any more comments befpre I bundle it up,
test and report?
Nope (not that I can comment on an incremental).
I guess I should create an empty Documentation/kvm/locking.txt and force
everyone else to
On Thu, Nov 18, 2010 at 01:03:44PM +0200, Avi Kivity wrote:
On 11/18/2010 12:57 PM, Michael S. Tsirkin wrote:
So the following on top will fix it all.
Any more comments befpre I bundle it up,
test and report?
Nope (not that I can comment on an incremental).
Here it is rolled up.
I
On Thu, Nov 18, 2010 at 12:18:27PM +0200, Gleb Natapov wrote:
On Wed, Nov 17, 2010 at 09:54:27PM +, Blue Swirl wrote:
2010/11/16 Gleb Natapov g...@redhat.com:
On Tue, Nov 16, 2010 at 06:30:19PM +, Blue Swirl wrote:
Perhaps the FW path should use device class names if no name is
On Thu, Nov 18, 2010 at 01:38:31PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 12:18:27PM +0200, Gleb Natapov wrote:
On Wed, Nov 17, 2010 at 09:54:27PM +, Blue Swirl wrote:
2010/11/16 Gleb Natapov g...@redhat.com:
On Tue, Nov 16, 2010 at 06:30:19PM +, Blue Swirl
On Thu, Nov 18, 2010 at 01:45:04PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 01:38:31PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 12:18:27PM +0200, Gleb Natapov wrote:
On Wed, Nov 17, 2010 at 09:54:27PM +, Blue Swirl wrote:
2010/11/16 Gleb Natapov
On Thu, Nov 18, 2010 at 5:41 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 18, 2010 at 11:30:47AM +0200, Avi Kivity wrote:
*entry may be stale after rcu_read_unlock(). Is this a problem?
I suppose not. All MSI-X MMIO accessing would be executed without delay, so
no re-
On Thu, Nov 18, 2010 at 5:28 PM, Avi Kivity a...@redhat.com wrote:
On 11/18/2010 03:58 AM, Sheng Yang wrote:
On Wednesday 17 November 2010 21:58:00 Avi Kivity wrote:
On 11/15/2010 11:15 AM, Sheng Yang wrote:
This patch enable per-vector mask for assigned devices using MSI-X.
On Thu, Nov 18, 2010 at 01:52:30PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 01:45:04PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 01:38:31PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 12:18:27PM +0200, Gleb Natapov wrote:
On Wed, Nov 17, 2010 at
cea15c2 (KVM: Move KVM context switch into own function) split vmx_vcpu_run()
to prevent multiple copies of the context switch from being generated (causing
problems due to a label). This patch folds them back together again and adds
the __noclone attribute to prevent the label from being
On Thu, Nov 18, 2010 at 02:16:05PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 01:52:30PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 01:45:04PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 01:38:31PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at
On 11/18/2010 01:10 PM, Michael S. Tsirkin wrote:
I guess I should create an empty Documentation/kvm/locking.txt and
force everyone else to update it.
Comments near the relevant fields not better?
Not an either/or. You can't understand the system from random source
comments.
diff
On Thu, Nov 18, 2010 at 07:59:10PM +0800, Sheng Yang wrote:
On Thu, Nov 18, 2010 at 5:41 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 18, 2010 at 11:30:47AM +0200, Avi Kivity wrote:
*entry may be stale after rcu_read_unlock(). Is this a problem?
I suppose not. All
On Thu, Nov 18, 2010 at 02:23:20PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 02:16:05PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 01:52:30PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 01:45:04PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at
On Thu, Nov 18, 2010 at 8:33 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 18, 2010 at 07:59:10PM +0800, Sheng Yang wrote:
On Thu, Nov 18, 2010 at 5:41 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 18, 2010 at 11:30:47AM +0200, Avi Kivity wrote:
*entry may be
On 11/18/2010 07:14 AM, Takuya Yoshikawa wrote:
This patch introduces the counter to hold the number of dirty bits in each
memslot. We will use this to optimize dirty logging later.
@@ -3217,11 +3216,8 @@ int kvm_vm_ioctl_get_dirty_log(struct kvm *kvm,
n =
On Thu, Nov 18, 2010 at 02:29:11PM +0200, Avi Kivity wrote:
On 11/18/2010 01:10 PM, Michael S. Tsirkin wrote:
I guess I should create an empty Documentation/kvm/locking.txt and
force everyone else to update it.
Comments near the relevant fields not better?
Not an either/or. You
On 11/18/2010 07:15 AM, Takuya Yoshikawa wrote:
Lai Jiangshan once tried to rewrite kvm_mmu_slot_remove_write_access() using
rmap: kvm: rework remove-write-access for a slot
http://www.spinics.net/lists/kvm/msg35871.html
One problem pointed out there was that this approach might hurt
On 11/18/2010 03:03 PM, Michael S. Tsirkin wrote:
int kvm_set_irq(struct kvm *kvm, int irq_source_id, u32 irq, int level);
+int kvm_set_msi(struct kvm_kernel_irq_routing_entry *irq_entry, struct kvm
*kvm,
+ int irq_source_id, int level);
No point in the level argument
Am 18.11.2010 13:54, Avi Kivity wrote:
On 11/18/2010 07:14 AM, Takuya Yoshikawa wrote:
This patch introduces the counter to hold the number of dirty bits in
each
memslot. We will use this to optimize dirty logging later.
@@ -3217,11 +3216,8 @@ int kvm_vm_ioctl_get_dirty_log(struct kvm *kvm,
On Thu, Nov 18, 2010 at 02:37:08PM +0200, Gleb Natapov wrote:
So that's unavoidable if we think paths are correct.
But if we know they are wrong, we are better off
correcting them first IMO.
They are correct for x86. My patch set does not even tries to cover all
HW. If sparc want to use
Hello,
Am Donnerstag 18 November 2010 10:05:59 schrieb Hidetoshi Seto:
Your have to be careful about compile-time-detection and
runtime-detection:
...
-#ifdef CONFIG_UTIMENSAT
-return utimensat(dirfd, path, times, flags);
-#else
+{
+int ret = utimensat(dirfd, path, times,
On 11/18/2010 03:10 PM, Jan Kiszka wrote:
Am 18.11.2010 13:54, Avi Kivity wrote:
On 11/18/2010 07:14 AM, Takuya Yoshikawa wrote:
This patch introduces the counter to hold the number of dirty bits in
each
memslot. We will use this to optimize dirty logging later.
@@ -3217,11 +3216,8
On Thu, Nov 18, 2010 at 03:03:37PM +0200, Michael S. Tsirkin wrote:
+static inline void kvm_irq_routing_update(struct kvm *kvm,
+struct kvm_irq_routing_table *irq_rt)
+{
+ rcu_assign_pointer(kvm-irq_routing, irq_rt);
+}
+
static inline int
On Thu, Nov 18, 2010 at 03:12:02PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 02:37:08PM +0200, Gleb Natapov wrote:
So that's unavoidable if we think paths are correct.
But if we know they are wrong, we are better off
correcting them first IMO.
They are correct for
On 11/18/2010 03:14 PM, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 03:03:37PM +0200, Michael S. Tsirkin wrote:
+static inline void kvm_irq_routing_update(struct kvm *kvm,
+ struct kvm_irq_routing_table
*irq_rt)
+{
+
On Thu, Nov 18, 2010 at 03:14:53PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 03:03:37PM +0200, Michael S. Tsirkin wrote:
+static inline void kvm_irq_routing_update(struct kvm *kvm,
+ struct kvm_irq_routing_table
*irq_rt)
+{
+
On Thu, Nov 18, 2010 at 03:20:27PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 03:14:53PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 03:03:37PM +0200, Michael S. Tsirkin wrote:
+static inline void kvm_irq_routing_update(struct kvm *kvm,
+
On 11/18/2010 03:35 PM, Gleb Natapov wrote:
or something like this.
Ah so you want to do it only for MSI? For MSI it makes sense. Remember
though that sometimes destination depend on message itself (specifically
on delivery mode).
Yes, broadcast or multicast or lowest priority wouldn't get
On 11/18/2010 1:17 PM, Avi Kivity wrote:
cea15c2 (KVM: Move KVM context switch into own function) split vmx_vcpu_run()
to prevent multiple copies of the context switch from being generated (causing
problems due to a label). This patch folds them back together again and adds
the __noclone
On Thu, Nov 18, 2010 at 03:35:01PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 03:20:27PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 03:14:53PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 03:03:37PM +0200, Michael S. Tsirkin wrote:
+static inline void
On Thu, Nov 18, 2010 at 03:39:15PM +0200, Avi Kivity wrote:
On 11/18/2010 03:35 PM, Gleb Natapov wrote:
or something like this.
Ah so you want to do it only for MSI? For MSI it makes sense. Remember
though that sometimes destination depend on message itself (specifically
on delivery
2010/11/18 Avi Kivity a...@redhat.com:
On 11/18/2010 12:58 AM, Kenni Lund wrote:
Hi
I'm about to move a couple of virtual machines from a Fedora 11 system
to a new server with a more recent operating system and newer version
of KVM, etc.
One of the guests is a Windows Server 2003 Standard
On 11/18/2010 03:48 PM, Andi Kleen wrote:
On 11/18/2010 1:17 PM, Avi Kivity wrote:
cea15c2 (KVM: Move KVM context switch into own function) split
vmx_vcpu_run()
to prevent multiple copies of the context switch from being generated
(causing
problems due to a label). This patch folds them back
On Thu, Nov 18, 2010 at 03:48:43PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 03:35:01PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at 03:20:27PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 18, 2010 at 03:14:53PM +0200, Gleb Natapov wrote:
On Thu, Nov 18, 2010 at
On 11/18/2010 09:05 AM, Kenni Lund wrote:
2010/11/18 Avi Kivity a...@redhat.com:
On 11/18/2010 12:58 AM, Kenni Lund wrote:
Hi
I'm about to move a couple of virtual machines from a Fedora 11 system
to a new server with a more recent operating system and newer version
of KVM, etc.
One of
On Thu, 2010-11-18 at 12:44 -0200, Lucas Meneghel Rodrigues wrote:
From: Jason Wang jasow...@redhat.com
This patch does the following things:
- Drop the built-in tftp/dhcp based unatteded installation for the
following reason:
1 It's based on slirp and was not supported by major
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.37
To receive the following updates:
Avi Kivity (2):
KVM: Correct ordering of ldt reload wrt fs/gs reload
KVM: VMX: Fix host userspace gsbase corruption
arch/x86/kvm/svm.c |2 +-
On 11/18/2010 3:32 PM, Avi Kivity wrote:
On 11/18/2010 03:48 PM, Andi Kleen wrote:
On 11/18/2010 1:17 PM, Avi Kivity wrote:
cea15c2 (KVM: Move KVM context switch into own function) split
vmx_vcpu_run()
to prevent multiple copies of the context switch from being
generated (causing
problems due
On 11/18/2010 05:00 PM, Andi Kleen wrote:
On 11/18/2010 3:32 PM, Avi Kivity wrote:
On 11/18/2010 03:48 PM, Andi Kleen wrote:
On 11/18/2010 1:17 PM, Avi Kivity wrote:
cea15c2 (KVM: Move KVM context switch into own function) split
vmx_vcpu_run()
to prevent multiple copies of the context switch
On 11/18/2010 01:42 AM, Anthony Liguori wrote:
Gack. For the benefit of those that want to join the fun without
digging up the spec, these magic flippable segments the i440fx can
toggle are 12 fixed 16k segments from 0xc to 0xe and a single
64k segment from 0xf to 0xf. There
On 11/18/2010 09:22 AM, Avi Kivity wrote:
On 11/18/2010 01:42 AM, Anthony Liguori wrote:
Gack. For the benefit of those that want to join the fun without
digging up the spec, these magic flippable segments the i440fx can
toggle are 12 fixed 16k segments from 0xc to 0xe and a single
64k
On Wed, Nov 17, 2010 at 05:42:28PM -0600, Anthony Liguori wrote:
For my purpose in using this to program the IOMMU with guest physical to
host virtual addresses for device assignment, it doesn't really matter
since there should never be a DMA in this range of memory. But for a
general RAM
On 11/18/2010 05:46 PM, Anthony Liguori wrote:
On 11/18/2010 09:22 AM, Avi Kivity wrote:
On 11/18/2010 01:42 AM, Anthony Liguori wrote:
Gack. For the benefit of those that want to join the fun without
digging up the spec, these magic flippable segments the i440fx can
toggle are 12 fixed 16k
On 11/18/2010 09:57 AM, Avi Kivity wrote:
On 11/18/2010 05:46 PM, Anthony Liguori wrote:
On 11/18/2010 09:22 AM, Avi Kivity wrote:
On 11/18/2010 01:42 AM, Anthony Liguori wrote:
Gack. For the benefit of those that want to join the fun without
digging up the spec, these magic flippable
On Wed, Nov 17, 2010 at 01:40:49PM +0200, Avi Kivity wrote:
A couple of trivial patches that clean up a bit of cruft from the emulator.
Avi Kivity (2):
KVM: x86 emulator: drop unused #ifndef __KERNEL__
KVM: x86 emulator: drop DPRINTF()
arch/x86/kvm/emulate.c | 14 +-
1
On Thu, Nov 18, 2010 at 03:12:56PM +0800, Xiao Guangrong wrote:
On 11/17/2010 11:57 PM, Avi Kivity wrote:
set_pte:
update_spte(sptep, spte);
+/*
+ * If we overwrite a writable spte with a read-only one we
+ * should flush remote TLBs. Otherwise rmap_write_protect
On Tue, Nov 16, 2010 at 05:32:44PM +0900, Takuya Yoshikawa wrote:
Hello!
During investigating kvm's mutual exclusions, starting from checking
kvm's srcu grace periods, I could not understand some of the locking rules.
This one is an example which I doubt.
But I'm not so sure. Please
On Wed, Nov 17, 2010 at 03:28:20PM +0200, Avi Kivity wrote:
Currently we lose segment information associated with memory operands. This
prevents us from doing proper segment checks.
This patchset prepares the way by remembering which segment is associated
with a memory operand.
Avi
On Wed, Nov 17, 2010 at 11:40:17AM +0800, Shane Wang wrote:
Inform user to either disable TXT in the BIOS or do TXT launch with tboot
before enabling KVM since some BIOSes do not set
FEATURE_CONTROL_VMXON_ENABLED_OUTSIDE_SMX bit when TXT is enabled.
Signed-off-by: Shane Wang
On 11/18/2010 06:09 PM, Anthony Liguori wrote:
That's what two memory maps mean. If you have one cpu in SMM and
another outside SMM, then those two maps are active simultaneously.
I'm not sure if more modern memory controllers do special things here,
but for the i440fx, if any CPU asserts
On Thu, Nov 18, 2010 at 06:18:06PM +0200, Avi Kivity wrote:
But for PV devices, we can be loose in how we define the way the
devices interact with the rest of the system. For instance, we
can say that virtio-pci devices are directly connected to RAM and
do not go through the memory
On 11/18/2010 05:32 PM, Marcelo Tosatti wrote:
There is no need to flush on sync_page path since the guest is
responsible for it.
If we don't, the next rmap_write_protect() will incorrectly decide that
there's no need to flush tlbs.
Maybe it's not a problem if guest
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly without bouncing out to
a kernel thread.
While we touch this structure, rearrange irqfd fields to make fastpath
better packed for better cache utilization.
This also adds some comments about locking rules
2010/11/18 Cole Robinson crobi...@redhat.com:
On 11/18/2010 09:05 AM, Kenni Lund wrote:
I'm curious why the RHEL 6 documentation claims that you actively need
to select the Standard PC HAL on installation, if it's not even the
recommended/preferred HAL...(?):
Windows 2003 requires a specific
v3:
- Address review comments
- pc registers all memory below 4G in one chunk
Let me know if there are any further issues. Thanks,
Alex
v2:
- Move to Makefile.objs
- Move structures to memory.c and create a callback function
- Fix memory leak
I haven't moved to the state parameter
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Makefile.objs |1 +
cpu-common.h |2 +
memory.c | 97
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/pc.c |9 +++--
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 69b13bf..fb7ee21 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -912,14 +912,11 @@
Hi,
I searched the archive found some discutions about this, not fixed yet?
could someone tell, is g4 kvm available now?
powerpc g4 build failed (host kernel 2.6.37-rc2):
CCppc-softmmu/kvm.o
/home/dave/qemu-kvm/target-ppc/kvm.c: In function 'kvm_arch_init_vcpu':
(2010/11/19 15:01), Yang Rui Rui wrote:
Hi,
I searched the archive found some discutions about this, not fixed yet?
could someone tell, is g4 kvm available now?
Hi, (added kvm-ppc to Cc)
I'm using g4 (Mac mini box) to run KVM.
- though not tried 2.6.37-rc2 yet.
Aren't you using upstream
On 11/19/2010 02:24 PM, Takuya Yoshikawa wrote:
(2010/11/19 15:01), Yang Rui Rui wrote:
Hi,
I searched the archive found some discutions about this, not fixed yet?
could someone tell, is g4 kvm available now?
Hi, (added kvm-ppc to Cc)
I'm using g4 (Mac mini box) to run KVM.
- though not
On 11/19/2010 02:37 PM, Yang Ruirui R wrote:
On 11/19/2010 02:24 PM, Takuya Yoshikawa wrote:
(2010/11/19 15:01), Yang Rui Rui wrote:
Hi,
I searched the archive found some discutions about this, not fixed yet?
could someone tell, is g4 kvm available now?
Hi, (added kvm-ppc to Cc)
I'm using
Aren't you using upstream qemu?
IIRC, ppc kvm needs to use upstream qemu.
I use qemu-kvm git version. Do you means qemu instead of qemu-kvm?
Hi, qemu 0.13.0 build passed
Yes, that what I meant!
Takuya
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
http://maralemprendimientos.com/important.php
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
(2010/11/19 15:01), Yang Rui Rui wrote:
Hi,
I searched the archive found some discutions about this, not fixed yet?
could someone tell, is g4 kvm available now?
Hi, (added kvm-ppc to Cc)
I'm using g4 (Mac mini box) to run KVM.
- though not tried 2.6.37-rc2 yet.
Aren't you using upstream
91 matches
Mail list logo
