Now that more platforms are joining the KVM wagon, we should define
a
common bus. PCI was a overkill anyway - its irq are shared and we
don't
have to use its io/mmio areas.
Do you guys have something to start with?
We do have something basic, our vdev bus. The bad thing is, it is
I want to try the balloon driver. Do we have it in any git tree?
The git tree I am having now only has master branch, and nothing
else.
(Maybe the balloon driver is not working yet, but I am curious when
see the userspace code in user/)
Thanks,
Jun
You're welcome to test it, it is
Jun Koi wrote:
So the PCI interface is definetely better IMO. Please put it online,
so we can test it.
Why would we want a PCI interface to do balooning? All we need is a
simple interface. It _is_ a mess for platforms that don't have PCI.
And it is a mess for paravirtulaization - will we create
Dor Laor wrote:
I agree that pci interface isn't ideal, the advantage is that platforms
that do support pci don't have to implement a virtualized bus, and pci
is PnP device. This was the motivation behind using it, especially for
Windows.
In understand that requirement, and I think being able
On Wednesday 06 June 2007, Carsten Otte wrote:
Dor Laor wrote:
Now that more platforms are joining the KVM wagon, we should define a
common bus. PCI was a overkill anyway - its irq are shared and we don't
have to use its io/mmio areas.
Do you guys have something to start with?
We do
On 6/7/07, Avi Kivity [EMAIL PROTECTED] wrote:
Carsten Otte wrote:
The best approach into this direction I have seen so far is not our
own vdev thing but Rusty's virtio infrastructure. That's what I think
I would start with.
I agree. We need a Lego set containing the following
Arnd Bergmann wrote:
On Wednesday 06 June 2007, Carsten Otte wrote:
We do have something basic, our vdev bus. The bad thing is, it is
platform specific. I really prefer to aim for an idea that Arnd came
up with when discussing this issue:
We could define a virtual device bus.
I guess,
Jun Koi wrote:
On 6/7/07, Avi Kivity [EMAIL PROTECTED] wrote:
Carsten Otte wrote:
The best approach into this direction I have seen so far is not our
own vdev thing but Rusty's virtio infrastructure. That's what I think
I would start with.
I agree. We need a Lego set containing the
Carsten Otte wrote:
So you suggest having a PCI driver that exports a virtio device for
each PCI device it matches? Sounds fine to me, though it goes beyond
what I think Rusty had in mind with his latest set of virtio
patches.
We don't need a PCI device per virtio device. We can have a
On Wed, 2007-06-06 at 19:17 +0300, Avi Kivity wrote:
Carsten Otte wrote:
The best approach into this direction I have seen so far is not our
own vdev thing but Rusty's virtio infrastructure. That's what I think
I would start with.
I agree. We need a Lego set containing the
Hi,
I want to try the balloon driver. Do we have it in any git tree?
The git tree I am having now only has master branch, and nothing else.
(Maybe the balloon driver is not working yet, but I am curious when
see the userspace code in user/)
Thanks,
Jun
Hi,
I want to try the balloon driver. Do we have it in any git tree?
The git tree I am having now only has master branch, and nothing else.
(Maybe the balloon driver is not working yet, but I am curious when
see the userspace code in user/)
Thanks,
Jun
You're welcome to test it, it is under
Hi Dor,
On 6/5/07, Dor Laor [EMAIL PROTECTED] wrote:
Hi,
I want to try the balloon driver. Do we have it in any git tree?
The git tree I am having now only has master branch, and nothing else.
(Maybe the balloon driver is not working yet, but I am curious when
see the userspace code in
13 matches
Mail list logo
