Hollis Blanchard wrote:
> These small ifdefs are necessary for integration of the PowerPC port.
>
>
Only patch 2 of 2 made it.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponso
Hollis Blanchard wrote:
> # HG changeset patch
> # User Hollis Blanchard <[EMAIL PROTECTED]>
> # Date 1200434370 21600
> # Node ID 9878c9cec5f831ff5e9b97539aabc5fa3d934501
> # Parent 931a81e1002110be0e8bf5b335bf199d43534c2c
> This allows kvm_host.h to be #included even when struct preempt_notifier
Hollis Blanchard wrote:
> # HG changeset patch
> # User Hollis Blanchard <[EMAIL PROTECTED]>
> # Date 1200436754 21600
> # Node ID c6e8bf3f9f7c9705a0ad29f44fa148fe80a365ff
> # Parent f22e390c06b78ffbcec4738112309f66267e3582
> This will allow other architectures to share it, since main.c is x86-onl
Glauber de Oliveira Costa wrote:
> +static void kvm_write_guest_time(struct kvm_vcpu *v)
> +{
> + struct timespec ts, wc_ts;
> + int wc_args[3]; /* version, wc_sec, wc_nsec */
> + unsigned long flags;
> + struct kvm_vcpu_arch *vcpu = &v->arch;
> + struct xen_shared_info *shared
Glauber de Oliveira Costa wrote:
> kvm_para.h potentially contains definitions that are to be used by
> kvm-userspace,
> so it should not be included inside the __KERNEL__ block. To protect its own
> data structures,
> kvm_para.h already includes its own __KERNEL__ block.
>
>
Applied this one
[fixing gmane emails, urgfhsz]
Andi Kleen wrote:
> Avi Kivity writes:
>
>
>> Thanks; that's reassuring to know that it will work (at least on Intel).
>>
>
> Actually there are modern Intel systems which still have instable TSCs;
> e.g. IBM Summit multi node systems and some others. So you
Hi,
> We want to avoid updating wall clock all the time. As far as I
> understand, wall clock is just a base which doesn't change.
Yep, it is. Got that wrong first in xenner, with the result that guest
time ran at double speed ;)
>> +/* xen binary-compatible interfaces. See xen headers for
Avi Kivity wrote:
> Hollis Blanchard wrote:
>> These small ifdefs are necessary for integration of the PowerPC port.
>>
>>
>
> Only patch 2 of 2 made it.
>
As Hollis should be sleeping right now I resend 1/2 as it arrived on
kvm-powerpc-devel
(I hope my mail-app keeps the format this time)
-
Gerd Hoffmann wrote:
> Hi,
>
>
>> We want to avoid updating wall clock all the time. As far as I
>> understand, wall clock is just a base which doesn't change.
>>
>
> Yep, it is. Got that wrong first in xenner, with the result that guest
> time ran at double speed ;)
>
>
>>> +/* xen
Subject: [PATCH] add more regs to kvm_show_regs for powerpc
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This adds some registers useful for guest debugging to the powerpc code for
kvm_show_regs in libkvm.
Signed-off-by: Christian Ehrhardt <[EMAIL PROTECTED]>
libkvm-powerpc.c |4
1 fi
I just read the ChangeLogs from kvm-47 to kvm-59 but I didn't notice
anything that about PCI pass-through or any VGA work. I'm curious how
things are going and what method was selected to accomplish this
functionality?
- Tony
Dor Laor wrote:
> It's still out-of -tree.
> Not for long :)
>
> Ant
On Wed, Jan 16, 2008 at 10:46:11AM +0200, Avi Kivity wrote:
> [fixing gmane emails, urgfhsz]
>
> Andi Kleen wrote:
> >Avi Kivity writes:
> >
> >
> >>Thanks; that's reassuring to know that it will work (at least on Intel).
> >>
> >
> >Actually there are modern Intel systems which still have
On Wed, Jan 16, 2008 at 03:38:45PM +0200, Avi Kivity wrote:
> Andi Kleen wrote:
> >Linux checks a couple of things: e.g. if there are no deep C states
> >and if there are no clustered nodes in the APIC etc.
> >
> >It might be reasonable to check the clock source of the kernel
> >and if it's not TSC
Andi Kleen wrote:
> Check if host is using TSC source and if not force a clustered
> APIC mode (only works for 64bit unfortunately) or fake a C3 state
> in ACPI and on AMD clear the synchronous TSC bit.
>
Yes, I got similar suggestions from Thomas. But it looks like older
guests will need a b
Laurent Vivier wrote:
> Le mardi 15 janvier 2008 à 23:54 +, Daniel P. Berrange a écrit :
>
>> On Wed, Jan 16, 2008 at 12:40:06AM +0100, Laurent Vivier wrote:
>>
>>> Le mardi 15 janvier 2008 à 18:27 +, Daniel P. Berrange a écrit :
>>>
On Tue, Jan 15, 2008 at 07:22:53PM +0
Le mercredi 16 janvier 2008 à 08:57 -0600, Anthony Liguori a écrit :
> > Le mardi 15 janvier 2008 à 23:54 +, Daniel P. Berrange a écrit :
[...]
> >>> 2- I'd like to mount qcow2 or others disk image formats, so perhaps it's
> >>> easier to modify loop device driver (but perhaps you know another
Due to Qumranet relocating to new premises, the kvm wiki will be down
tomorrow for at least a few hours.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Microsoft
Defy al
On Wed, 2008-01-16 at 10:08 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > # HG changeset patch
> > # User Hollis Blanchard <[EMAIL PROTECTED]>
> > # Date 1200434370 21600
> > # Node ID 9878c9cec5f831ff5e9b97539aabc5fa3d934501
> > # Parent 931a81e1002110be0e8bf5b335bf199d43534c2c
> > This
I think I've misunderstood what you guys wanted to achieve with "xen
compatible", but now I get it. It's something that's kvm specific,
but happens to be able to communicate with xen guests, provided they
do a kvm-aware initialization.
So, here's the two patches for it, using two msrs and non-xe
This is the host part of kvm clocksource implementation. As it does
not include clockevents, it is a fairly simple implementation. We
only have to register a per-vcpu area, and start writting to it periodically.
The area is binary compatible with xen, as we use the same shadow_info
structure.
Si
This is the guest part of kvm clock implementation
It does not do tsc-only timing, as tsc can have deltas
between cpus, and it did not seem worthy to me to keep
adjusting them.
We do use it, however, for fine-grained adjustment.
Other than that, time comes from the host.
Signed-off-by: Glauber d
Dan Kenigsberg wrote:
> On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
>
>> Dan Kenigsberg wrote:
>>
>>> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
>>>
>>>
Hi,
Currently CPUID function 4 is broken. This function's values rely on
On Sun, 13 Jan 2008 17:24:18 +0100
Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> In my basic initial patch I only track the tlb flushes which should be
> the minimum required to have a nice linux-VM controlled swapping
> behavior of the KVM gphysical memory.
I have a vaguely related question on
Dear Reader, You are invited to attend the 8th
Annual National Multicultural Business Conference. The event on April 23 -25, 2008 bringing together Small Businesses, Government Agencies and Fortune 1000 companies for promoting business opportunities. Attendance is expected to top 1200. This yea
Rik van Riel wrote:
> On Sun, 13 Jan 2008 17:24:18 +0100
> Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
>
>
>> In my basic initial patch I only track the tlb flushes which should be
>> the minimum required to have a nice linux-VM controlled swapping
>> behavior of the KVM gphysical memory.
>>
On Wed, 16 Jan 2008, Avi Kivity wrote:
> Yes, that was poorly phrased. The page and its page struct may
be reallocated
> for other purposes.
Its better to say "reused". Otherwise one may think that an allocation of
page structs is needed.
--
Glauber de Oliveira Costa wrote:
> This is the host part of kvm clocksource implementation. As it does
> not include clockevents, it is a fairly simple implementation. We
> only have to register a per-vcpu area, and start writting to it periodically.
>
> The area is binary compatible with xen, as w
On Wed, Jan 16, 2008 at 06:34:08PM +0100, Alexander Graf wrote:
> Dan Kenigsberg wrote:
> > On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
> >
> >> Dan Kenigsberg wrote:
> >>
> >>> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
> >>>
> >>>
>
When it's more close to inclusion, I'd also post it to main qemu list.
But right now, I'm just aiming at a first round around this draft.
The attached patch is enough to make the notifications DEVICE_CHECK and
EJECT reach the kernel. As far as I understand, some userspace black
magic that keep
On Wed, 2008-01-16 at 13:05 +0100, Anthony de Almeida Lopes wrote:
> I just read the ChangeLogs from kvm-47 to kvm-59 but I didn't notice
> anything that about PCI pass-through or any VGA work. I'm curious how
> things are going and what method was selected to accomplish this
> functionality?
>
On Tue, 2008-01-15 at 17:01 -0200, Marcelo Tosatti wrote:
> OK, thats simpler. How about this:
>
It's sure is simpler :)
> [PATCH] Virtio balloon driver
>
> Add a balloon driver for KVM, host<->guest communication is performed
> via virtio.
>
> Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTE
Anthony Liguori wrote:
> Glauber de Oliveira Costa wrote:
>> This is the host part of kvm clocksource implementation. As it does
>> not include clockevents, it is a fairly simple implementation. We
>> only have to register a per-vcpu area, and start writting to it
>> periodically.
>>
>> The area i
After discussions with Anthony Liguori, it seems that the virtio
balloon can be made even simpler. Here's my attempt.
Since the balloon requires Guest cooperation anyway, there seems
little reason to force it to tell the Host when it wants to reuse a
page. It can simply fault it in.
Moreover, t
Rusty Russell wrote:
> After discussions with Anthony Liguori, it seems that the virtio
> balloon can be made even simpler. Here's my attempt.
>
> Since the balloon requires Guest cooperation anyway, there seems
> little reason to force it to tell the Host when it wants to reuse a
> page. It can
On Thursday 17 January 2008 13:14:58 Anthony Liguori wrote:
> Rusty Russell wrote:
> > +static struct virtio_device_id id_table[] = {
> > + { VIRTIO_ID_BALLOON, VIRTIO_DEV_ANY_ID},
>
> Could use a space after VIRTIO_DEV_ANY_ID
Thanks, fixed.
> > + __free_page(page);
> > + vb
Rusty Russell wrote:
> On Thursday 17 January 2008 13:14:58 Anthony Liguori wrote:
>
>> Rusty Russell wrote:
>>
>>> +static struct virtio_device_id id_table[] = {
>>> + { VIRTIO_ID_BALLOON, VIRTIO_DEV_ANY_ID},
>>>
>> Could use a space after VIRTIO_DEV_ANY_ID
>>
>
> Thanks, fix
On Thursday 17 January 2008 15:01:46 Anthony Liguori wrote:
> Rusty Russell wrote:
> > OTOH it's currently pretty obvious (and usually fatal) if the guest has
> > trouble meeting the balloon requirements. A serious host needs a way of
> > detecting stress in the guest anyway, which this doesn't of
Hi, Avi/Tony
This patch exports three symbols out for module use. Please
comments! :)
Thanks
Xiantao
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thu, 17 Jan 2008 14:03:04 +0800
Subject: [PATCH] kvm: ia64 : Export some symbols out for module use.
Export empty_zero_page, ia64_sal_cache
On Jan 16, 2008, at 9:12 PM, Dan Kenigsberg wrote:
> On Wed, Jan 16, 2008 at 06:34:08PM +0100, Alexander Graf wrote:
>> Dan Kenigsberg wrote:
>>> On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
>>>
Dan Kenigsberg wrote:
> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Ale
Glauber de Oliveira Costa wrote:
> This is the host part of kvm clocksource implementation. As it does
> not include clockevents, it is a fairly simple implementation. We
> only have to register a per-vcpu area, and start writting to it periodically.
>
> The area is binary compatible with xen, as
40 matches
Mail list logo
