Dor Laor wrote:
>> Can you elaborate here? Using a PCI discover mechanism, you've got
>> your memory already. Not point in reinventing PCI with hypercalls.
>>
> In this case I agree that it should be done using pci/other_bus config
> space.
>
>>> 2. For other purposes such as a balloon
Cam Macdonell wrote:
Dor Laor wrote:
>>> You need to open the unix socket you passed to the vmchannel
>>> parameter.
>>> An easier alternative is to use -vmchannel di:2258,tcp://
>>> 0:,server.
>>> Before the guest loads you'll need to telnet the port and then
>>> you should receive the
Anthony Liguori wrote:
> Dor Laor wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>
Dor Laor wrote:
>> Hi all,
>>
>> I've finally started looking at Dor's git tree, and it struck me
>>
> that
>
>> it conflicts w
Dong, Eddie wrote:
>> The push model may require parallelization of the disk and memory
>> convergence depending on how much disk activity the guest is doing.
>> That's a pretty interesting problem but it shouldn't be too
>> hard to solve.
>>
>>
> Embed this kind of cache like disk ops (wr
Nakajima, Jun wrote:
> Jeremy Fitzhardinge wrote:
>
>> Nakajima, Jun wrote:
>>
>>> The hypervisor detection machanism is generic, and the signature
>>> returned is implentation specific. Having a list of all hypervisor
>>> signatures sounds fine to me as we are detecting vendor-specific
>>>
This patch refactors the current hypercall infrastructure to better support live
migration and SMP. It eliminates the hypercall page by trapping the UD
exception that would occur if you used the wrong hypercall instruction for the
underlying architecture and replacing it with the right one lazily.
This adds a CPUID entry for the paravirtualization feature bitmap. We can do
this unconditionally because the guest requires that both the feature CPUID
entry and the signature CPUID entry exists to enable paravirtualization.
This means that guest will never enable paravirtualization if either us
Zachary Amsden wrote:
> On Fri, 2007-09-14 at 16:44 -0500, Anthony Liguori wrote:
>
>
>> So then each module creates a hypercall page using this magic MSR and
>> the hypervisor has to keep track of it so that it can appropriately
>> change the page on migration. The page can only contain a si
Dor Laor wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>
>>> Dor Laor wrote:
>>>
> Hi all,
>
> I've finally started looking at Dor's git tree, and it struck me
>
that
> it conflicts with Anthony's hypercall patches. F
Hi list,
I mailed about this earlier (may 7th, 2007) but the issue is still there: the
handling surrounding DHCP clients could be a bit improved...
Currently every dhcp client gets killed after which a very basic dhcp client is
started for the dst interface, which is not really inline with wh
Ah, I need to get that how-to up, only Anthony tried it and he never
seems to need a HOWTO :-)
thanks, I am glad you are interested, I will test it again and
probably put a HOWTO up at linuxbios.org, which could be cloned at the
kvm web site.
ron
-
Rusty Russell wrote:
> On Sat, 2007-09-15 at 11:05 +0300, Avi Kivity wrote:
>
>> Rusty Russell wrote:
>>
>>> On Sat, 2007-09-15 at 01:31 +0300, Dor Laor wrote:
>>>
>>>
Second, regardless of the channel signal notification, there are still
real necessities for userspace
On Sat, 2007-09-15 at 11:05 +0300, Avi Kivity wrote:
> Rusty Russell wrote:
> > On Sat, 2007-09-15 at 01:31 +0300, Dor Laor wrote:
> >
> >> Second, regardless of the channel signal notification, there are still
> >> real necessities for userspace hypercall handling:
> >> 1. For virtio drivers t
On Fri, Sep 14, 2007 at 02:18:48PM -0500, Phil Lahman wrote:
> Greetings,
> I am trying to duplicate what I have done with the Free version of
> VmWare server, with KVM. Linux, Fedora 7 host and Fedora Core 3 guest..
>
> Since the KVM with fedora 7 is not current I decided to try and bui
Zachary Amsden wrote:
> On Fri, 2007-09-14 at 16:44 -0500, Anthony Liguori wrote:
>
>
>> So then each module creates a hypercall page using this magic MSR and
>> the hypervisor has to keep track of it so that it can appropriately
>> change the page on migration. The page can only contain a si
Rusty Russell wrote:
> On Sat, 2007-09-15 at 01:31 +0300, Dor Laor wrote:
>
>> Second, regardless of the channel signal notification, there are still
>> real necessities for userspace hypercall handling:
>> 1. For virtio drivers there is also registration hypercall for passing
>> the shared me
Nakajima, Jun wrote:
> To me this is the beginning of fragmentation. Why do we need different
> and VMM-specific Linux paravirtualization for hardware-assisted
> virtualization? That would not be good for Linux.
>
>
The only way to have a single interface is if a central authority
defines and d
Dor Laor wrote:
> Avi Kivity wrote:
>
>> Anthony Liguori wrote:
>>
>>
>>> Dor Laor wrote:
>>>
>>>
>>>
> Hi all,
>
> I've finally started looking at Dor's git tree, and it struck me
>
>
>
>
that
Anthony Liguori wrote:
> Jeremy Fitzhardinge wrote:
>
>> Anthony Liguori wrote:
>>
>>
>>> This patch refactors the current hypercall infrastructure to better support
>>> live
>>> migration and SMP. It eliminates the hypercall page by trapping the UD
>>> exception that would occur if yo
Nitin A Kamble wrote:
> Hi Avi,
>Attached is the patch to implement instruction:
> mov rl/rh/r, imm
> opcodes: 0xb0 - 0xbf
>
> case 0xb0 ... 0xb3: /* mov rl, imm8 */
> + dst.ptr = (unsigned long *)&_regs[VCPU_REGS_RAX + (b & 0x3)];
> + dst.val =
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement emulation of instruction:
> popf
> opcode: 0x9d
>
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to initialize src.val & dst.val. Without this,
> certain instructions are getting affected in their emulation.
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
---
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement instruction:
> jump absolute
> opcode: 0xff /4
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement instructions:
> inc reg
> opcode: 0x40 - 0x47
> Please apply.
>
> @@ -1390,6 +1393,22 @@ pop_instruction:
> _eip = ctxt->vcpu->rip;
> }
> switch (b) {
> + case 0x40 ... 0x47:
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement instruction:
> lea
> opcode: 0x8d
>
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
Nitin A Kamble wrote:
> Hi Avi,
> This patch corrects the emulation of the instruction "or" for opcodes
> 0xc & 0cd.
> Please Apply.
>
> + case 0x0c: /* or al imm8 */
> + dst.type = OP_REG;
> + dst.ptr = &_regs[VCPU_REGS_RAX];
> + dst.val
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement instruction:
> jump conditional relative (like: jnz jo etc)
> opcode : 0x0f80 - 0x0f8f
> Please apply.
>
>
Applied this and jump conditional short, thanks.
--
Do not meddle in the internals of kernels, for they
Nitin A Kamble wrote:
> The patch was empty in the last email. My mistake. Reattaching it.
>
> Thanks to Bernhard for pointing it out.
>
Thanks, applied.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
28 matches
Mail list logo
