各位老总：您们好！
诚祝：您们在2008年里；有鼠不尽的快乐！鼠不尽的收获！鼠不尽的钞票！
鼠不尽的幸福！鼠不尽的美满生活！愿： 您们阖家欢乐！幸福安康！
我是（深圳市珊湖岛进出口有限公司）的负责人；可以提供：出口报关单，
核销单等等一系列手续；代理：出口报关，商检，境内外运输..等等；还可
以代办：出口欧盟许可证，欧盟产地证；并且还有（广州国际贸易交易会）的摊
Amit Shah wrote:
-static int get_eoi_gsi(struct kvm_ioapic *ioapic, int vector)
+int get_eoi_gsi(struct kvm_ioapic *ioapic, int vector)
Such a generic name should be prefixed by kvm_ if you expose it.
--
error compiling committee.c: too many arguments to function
Amit Shah wrote:
Passthrough devices are host machine PCI devices which have
been handed off to the guest. Handle interrupts from these
devices and route them to the appropriate guest irq lines.
The userspace provides us with the necessary information
via the ioctls.
The guest IRQ numbers
Marcelo Tosatti wrote:
On Fri, Apr 11, 2008 at 03:12:41PM +0300, Avi Kivity wrote:
This breaks ia64 (and shouldn't s390 use this too?)
* We will block until either an interrupt or a signal wakes us up
*/
while (!kvm_cpu_has_interrupt(vcpu)
+
Carsten Otte wrote:
Avi Kivity wrote:
@@ -765,6 +766,7 @@ void kvm_vcpu_block(struct kvm_vcpu *vcp
This breaks ia64 (and shouldn't s390 use this too?)
* We will block until either an interrupt or a signal wakes us up
*/
while (!kvm_cpu_has_interrupt(vcpu)
+
Marcelo Tosatti wrote:
On Fri, Apr 11, 2008 at 03:18:19PM +0300, Avi Kivity wrote:
kvm_vcpu_kick() can be called from nonatomic contexts, so the vcpu-cpu
== cpu check is dangerous (and will warn on preemptible kernels, no?)
Doh, right. How's this.
---
KVM: fix
Bugs item #1941302, was opened at 2008-04-13 19:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1941302group_id=180599
Please note that this message will contain a full copy of
On Thu, 2008-04-10 at 11:48 +0300, Amit Shah wrote:
We can assign a device from the host machine to a guest.
A new command-line option, -pcidevice is added.
For example, to invoke it for an Ethernet device sitting at
PCI bus:dev.fn 04:08.0 with host IRQ 18, use this:
-pcidevice
各位老总：您们好！
诚祝：您们在2008年里；有鼠不尽的快乐！鼠不尽的收获！鼠不尽的钞票！
鼠不尽的幸福！鼠不尽的美满生活！愿： 您们阖家欢乐！幸福安康！
我是（深圳市珊湖岛进出口有限公司）的负责人；可以提供：出口报关单，
核销单等等一系列手续；代理：出口报关，商检，境内外运输..等等；还可
以代办：出口欧盟许可证，欧盟产地证；并且还有（广州国际贸易交易会）的摊
各位老总：您们好！
诚祝：您们在2008年里；有鼠不尽的快乐！鼠不尽的收获！鼠不尽的钞票！
鼠不尽的幸福！鼠不尽的美满生活！愿： 您们阖家欢乐！幸福安康！
我是（深圳市珊湖岛进出口有限公司）的负责人；可以提供：出口报关单，
核销单等等一系列手续；代理：出口报关，商检，境内外运输..等等；还可
以代办：出口欧盟许可证，欧盟产地证；并且还有（广州国际贸易交易会）的摊
Hi all,
in short: CentOS 5 guest (32bit) crashes when I run reboot in the VM
with qemu message:
kvm_run: failed entry, reason 65535
kvm_run returned -8
In dmesg is this message:
kvm: 23769: cpu0 kvm_set_msr_common: MSR_IA32_MC0_STATUS 0x0, nop
Details:
KVM 65
Host is openSUSE 10.3 with my own
Marcelo Tosatti wrote:
So userspace can save/restore the mpstate during migration.
Applied, thanks. I also added public #defines for the possible values.
--
error compiling committee.c: too many arguments to function
-
Marcelo Tosatti wrote:
Address comments from Avi:
- fold mp_state into a structure
- IOW/IOR markers for ioctl definitions
- return -ENOSYS if extension is not supported
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
Marcelo Tosatti wrote:
On Fri, Apr 11, 2008 at 01:59:35PM -0500, Anthony Liguori wrote:
With the IO thread, shouldn't we be striving to perform the select()s
within the IO thread itself to completely avoid the need to use SIGIO at
all?
Fully agree. Problem with it are the
On Sun, Apr 13, 2008 at 1:49 PM, Michal Ludvig [EMAIL PROTECTED] wrote:
Hi all,
in short: CentOS 5 guest (32bit) crashes when I run reboot in the VM
with qemu message:
kvm_run: failed entry, reason 65535
kvm_run returned -8
In dmesg is this message:
kvm: 23769: cpu0
Avi Kivity wrote:
@@ -3944,11 +3950,13 @@ static void vcpu_kick_intr(void *info)
void kvm_vcpu_kick(struct kvm_vcpu *vcpu)
{
int ipi_pcpu = vcpu-cpu;
+int cpu = get_cpu();
if (waitqueue_active(vcpu-wq)) {
wake_up_interruptible(vcpu-wq);
Marcelo Tosatti wrote:
With SIGIO enabled on stdio, there's no need to wakeup the thread
performing IO every 30ms.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index: kvm-userspace.io/qemu/vl.c
===
---
Avi Kivity wrote:
Avi Kivity wrote:
@@ -3944,11 +3950,13 @@ static void vcpu_kick_intr(void *info)
void kvm_vcpu_kick(struct kvm_vcpu *vcpu)
{
int ipi_pcpu = vcpu-cpu;
+int cpu = get_cpu();
if (waitqueue_active(vcpu-wq)) {
wake_up_interruptible(vcpu-wq);
With this, all the babes will flock to you. http://www.opeoteae.com/
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority
Hi,
I just tried the virtio block device with the intent
to boost disk throughput for my vm.
I ran bonnie++ -r 512 -s 2048 -u nobody -d /tmp:
Version 1.03 --Sequential Output-- --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
My understanding is that virtio is very latency-sensitive. Do you know
whether your system is configured for high-resolution timer support, and
(more to the point) which clock source KVM is using on your host?
-
This
Hi Charles,
thanks for the quick reply.
My understanding is that virtio is very latency-sensitive. Do you know
whether your system is configured for high-resolution timer support, and
(more to the point) which clock source KVM is using on your host?
On the host:
grep Clock Event Device
On Sun, Apr 13, 2008 at 11:04:44PM +0200, Gerd von Egidy wrote:
Hi,
I just tried the virtio block device with the intent
to boost disk throughput for my vm.
I ran bonnie++ -r 512 -s 2048 -u nobody -d /tmp:
Version 1.03 --Sequential Output-- --Sequential Input-
--Random-
On Sun, Apr 13, 2008 at 9:49 PM, Dor Laor [EMAIL PROTECTED] wrote:
On Thu, 2008-04-10 at 11:48 +0300, Amit Shah wrote:
If kvm uses the in-kernel irqchip, interrupts are routed to
the guest via the kvm module (accompanied kernel changes are necessar).
If -no-kvm-irqchip is used, the
I just took the old description that was there before. A much better one
would be:
Remove declarations of kvm_*_pit() on architectures who do not support
not have a PIT.
That is what I was really intending. It removes a lot of compile
warnings, when compiling anything with libkvm.h on platforms
Gerd von Egidy wrote:
Hi,
I just tried the virtio block device with the intent
to boost disk throughput for my vm.
We really haven't optimized virtio block yet under KVM. Most of the
effort so far has been focused on virtio_net. We'll get there though in
the near future.
Regards,
26 matches
Mail list logo
