On 06.07.2012, at 01:51, Scott Wood wrote:
> On 07/04/2012 08:40 AM, Alexander Graf wrote:
>> On 25.06.2012, at 14:26, Mihai Caraman wrote:
>>> @@ -381,7 +386,8 @@ static int kvmppc_booke_irqprio_deliver(struct kvm_vcpu
>>> *vcpu,
>>>set_guest_esr(vcpu, vcpu->arch.queued_esr);
>>>
On 07/06/2012 01:45 AM, Rick Jones wrote:
On 07/05/2012 03:29 AM, Jason Wang wrote:
Test result:
1) 1 vm 2 vcpu 1q vs 2q, 1 - 1q, 2 - 2q, no pinning
- Guest to External Host TCP STREAM
sessions size throughput1 throughput2 norm1 norm2
1 64 650.55 655.61 100% 24.88 24.86 99%
2 64 1446.81 13
On 07/06/2012 05:50 AM, Andrew Theurer wrote:
> I, and I expect others, have a keen interest in knowing how often we
> exit for PLE, and also how often that includes a yielding to another
> vcpu. The following adds two more counters to kvmstat to track the
> exits and the vcpu yields. This in no
On 07/06/2012 04:02 AM, Amos Kong wrote:
On 07/05/2012 06:29 PM, Jason Wang wrote:
This patch converts virtio_net to a multi queue device. After negotiated
VIRTIO_NET_F_MULTIQUEUE feature, the virtio device has many tx/rx queue pairs,
and driver could read the number from config space.
The driv
On 07/06/2012 04:07 AM, Amos Kong wrote:
On 07/05/2012 08:51 PM, Sasha Levin wrote:
On Thu, 2012-07-05 at 18:29 +0800, Jason Wang wrote:
@@ -1387,6 +1404,10 @@ static int virtnet_probe(struct virtio_device *vdev)
if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_VQ))
vi->
On Thu, Jul 5, 2012 at 7:58 PM, Jan Kiszka wrote:
> On 2012-07-05 13:02, liu ping fan wrote:
>> On Thu, Jul 5, 2012 at 6:16 PM, Jan Kiszka wrote:
>>> On 2012-07-05 12:10, liu ping fan wrote:
On Thu, Jul 5, 2012 at 2:46 PM, Jan Kiszka wrote:
> On 2012-07-05 04:18, Liu Ping Fan wrote:
>>>
From: Yanfei Zhang
Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill
VMCSINFO
Date: Wed, 4 Jul 2012 18:05:19 +0800
> Besides, this patch also exports vmcs revision identifier via
> /sys/devices/system/cpu/vmcs_id and offsets of fields via
> /sys/devices/system/cpu/vmcs/.
>
On Fri, 2012-07-06 at 11:20 +0800, Jason Wang wrote:
> On 07/05/2012 08:51 PM, Sasha Levin wrote:
> > On Thu, 2012-07-05 at 18:29 +0800, Jason Wang wrote:
> >> @@ -1387,6 +1404,10 @@ static int virtnet_probe(struct virtio_device *vdev)
> >> if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_VQ
On 2012-07-06 09:46, liu ping fan wrote:
> On Thu, Jul 5, 2012 at 7:58 PM, Jan Kiszka wrote:
>> On 2012-07-05 13:02, liu ping fan wrote:
>>> On Thu, Jul 5, 2012 at 6:16 PM, Jan Kiszka wrote:
On 2012-07-05 12:10, liu ping fan wrote:
> On Thu, Jul 5, 2012 at 2:46 PM, Jan Kiszka wrote:
>>>
On Fri, 2012-07-06 at 09:43 +0400, James Bottomley wrote:
> On Thu, 2012-07-05 at 20:01 -0700, Nicholas A. Bellinger wrote:
>
> > So I'm pretty sure this discrepancy is attributed to the small block
> > random I/O bottleneck currently present for all Linux/SCSI core LLDs
> > regardless of physical
At 07/06/2012 04:04 PM, HATAYAMA Daisuke Wrote:
> From: Yanfei Zhang
> Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill
> VMCSINFO
> Date: Wed, 4 Jul 2012 18:05:19 +0800
>
>> Besides, this patch also exports vmcs revision identifier via
>> /sys/devices/system/cpu/vmcs_id
On 07/06/2012 02:38 PM, Stephen Hemminger wrote:
On Fri, 06 Jul 2012 11:20:06 +0800
Jason Wang wrote:
On 07/05/2012 08:51 PM, Sasha Levin wrote:
On Thu, 2012-07-05 at 18:29 +0800, Jason Wang wrote:
@@ -1387,6 +1404,10 @@ static int virtnet_probe(struct virtio_device *vdev)
if (virt
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
Another purpose of this feature is: management app(for example:
libvirt) can do auto dump when the guest is panicked. If management
app does not do auto dump, the guest's user can do dump by hand
The guest should run after reseting it, but it does not run if its
old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
We don't set runstate to RUN_STATE_PAUSED when reseting the guest,
so the runstate will be changed from RUN_STATE_INTERNAL_ERROR or
RUN_STATE_PAUSED to RUN_STATE_RUNNING(no
Signed-off-by: Wen Congyang
---
linux-headers/asm-x86/kvm_para.h |2 ++
linux-headers/linux/kvm_para.h |6 ++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/linux-headers/asm-x86/kvm_para.h b/linux-headers/asm-x86/kvm_para.h
index f2ac46a..f9d858f 100644
--- a/linux-
The guest will be in this state when it is panicked.
Signed-off-by: Wen Congyang
---
qapi-schema.json |6 +-
qmp.c|3 ++-
vl.c |7 ++-
3 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 3b6e346..00
This event will be emited when the guest is panicked.
Signed-off-by: Wen Congyang
---
monitor.c |1 +
monitor.h |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monitor.c
index f6107ba..28f7482 100644
--- a/monitor.c
+++ b/monitor.c
@@ -458,6 +458,7 @@ sta
Hello all:
This seires is an update of last version of multiqueue support to add multiqueue
capability to both tap and virtio-net.
Some kinds of tap backends has (macvatp in linux) or would (tap) support
multiqueue. In such kind of tap backend, each file descriptor of a tap is a
qeueu and ioctls
Sometimes, we need to pass option like -netdev tap,fd=100,fd=101,fd=102 which
can not be properly parsed by qemu_find_opt() because it only returns the first
matched option. So qemu_get_opt_all() were introduced to return an array of
pointers which contains all matched option.
Signed-off-by: Jason
Some operating system ( such as Linux ) supports multiqueue tap, this is done
through attaching multiple sockets to the net device and expose multiple file
descriptors.
This patch let qemu utilizes this kind of backend, and introduces helpter for:
- creating a multiple capable tap device
- increa
This patch adds the multiqueues support for emulated nics. Each VLANClientState
pairs are now abstract as a queue instead of a nic, and multiple VLANClientState
pointers were stored in the NICState. A queue_index were also introduced to let
the emulated nics know which queue the packet were came fr
This patch converts the vhost to support multiqueue queues. It implement a 1:1
mapping of vhost devs and tap fds. That it to say, the patch creates and uses
N vhost devs as the backend of the N queues virtio-net deivce.
The main work is to convert the virtqueue index into vhost queue index, this i
Based on the multiqueue support for taps and NICState, this patch add the
capability of multiqueue for virtio-net. For userspace virtio-net emulation,
each pair of VLANClientState peers were abstracted as a tx/rx queue. For vhost,
the vhost net devices were created per virtio-net tx/rx queue pairs,
On Tue, 3 Jul 2012 04:55:35 -0300, Marcelo Tosatti wrote:
> On Mon, Jun 04, 2012 at 10:37:24AM +0530, Nikunj A. Dadhania wrote:
> > flush_tlb_others_ipi depends on lot of statics in tlb.c. Replicated
> > the flush_tlb_others_ipi as kvm_flush_tlb_others to further adapt to
> > paravirtualization.
https://bugzilla.kernel.org/show_bug.cgi?id=44271
Summary: kvm failure at boot up
Product: Virtualization
Version: unspecified
Kernel Version: 3.4.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
The action is the same as -onpanic parameter.
Signed-off-by: Wen Congyang
---
qemu-config.c |4
qemu-options.hx |4 +++-
vl.c|7 +++
3 files changed, 14 insertions(+), 1 deletions(-)
diff --git a/qemu-config.c b/qemu-config.c
index 5c3296b..805e7c4 100644
---
The onpanic parameter can have the following value:
1. none
2. pause
3. poweroff
4. reset
The action for each value when the guest is panicked:
1. none: emit QEVENT_GUEST_PANICKED only
2. pause: emit QEVENT_GUEST_PANICKED and pause the guest
3. poweroff: emit QEVENT_GUEST_PANICKED and poweroff the
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_PORT when it is panciked. This patch introduces a new qom
device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's value. The possible actions are:
1. emit QEVENT_GUES
hcd-ehci.c is missing an usb_packet_init() call for the ipacket UsbPacket
it uses for isoc transfers, triggering an assert (taking the entire vm down)
in usb_packet_setup as soon as any isoc transfers are done by a high speed
USB device.
Signed-off-by: Hans de Goede
---
hw/usb/hcd-ehci.c |1
Here are USB 2 bug-fixes, please also cherry-pick these into the
stable-1.1 branch, esp. the second one as that fixes an easily triggerable
assert.
Note these patches are against 1.1.0, not against master, but they are relevant
for, and should apply to, master too.
Regards,
Hans
--
To unsubscrib
Signed-off-by: Hans de Goede
---
hw/usb/redirect.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/usb/redirect.c b/hw/usb/redirect.c
index 5f55d78..c6358c0 100644
--- a/hw/usb/redirect.c
+++ b/hw/usb/redirect.c
@@ -1058,6 +1058,8 @@ static int usbredir_handle_status(USBRedirDevice *d
On 2012-07-06 11:38, Wen Congyang wrote:
> Signed-off-by: Wen Congyang
Which kvm.git hash is this referring? Please state this to avoid that we
are merging support for kernel features that are still under review.
Jan
> ---
> linux-headers/asm-x86/kvm_para.h |2 ++
> linux-headers/linux/kvm
Hi,
On 2012/06/29 23:56, Avi Kivity wrote:
>> On 2012/06/29 2:34, Avi Kivity wrote:
>>> On 06/28/2012 08:26 PM, Jan Kiszka wrote:
> This is both impressive and scary. What is the target scenario here?
> Partitioning? I don't see this working for generic consolidation.
From my P
At 07/06/2012 06:25 PM, Jan Kiszka Wrote:
> On 2012-07-06 11:38, Wen Congyang wrote:
>> Signed-off-by: Wen Congyang
>
> Which kvm.git hash is this referring? Please state this to avoid that we
> are merging support for kernel features that are still under review.
The following kvm.git:
http://gi
From: Wen Congyang
Subject: Re: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill
VMCSINFO
Date: Fri, 6 Jul 2012 16:25:23 +0800
> At 07/06/2012 04:04 PM, HATAYAMA Daisuke Wrote:
>> From: Yanfei Zhang
>> Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill
>> V
> > Which kvm.git hash is this referring? Please state this to avoid that we
> > are merging support for kernel features that are still under review.
>
> The following kvm.git:
> http://git.kernel.org/?p=virt/kvm/kvm.git;a=summary
What Jia ask for is git hash, should be something like,
8ac
On 2012-07-06 11:41, Wen Congyang wrote:
> If the target is x86/x86_64, the guest's kernel will write 0x01 to the
> port KVM_PV_PORT when it is panciked. This patch introduces a new qom
> device kvm_pv_ioport to listen this I/O port, and deal with panicked
> event according to panicked_action's val
On 2012-07-06 11:41, Wen Congyang wrote:
> The action is the same as -onpanic parameter.
As explained in patch 5, now that we have a related device, this no
longer needs to be a machine property.
Would could be a machine property is enabling/disabling this device.
That's probably useful as it use
On 2012-07-06 11:41, Wen Congyang wrote:
> The onpanic parameter can have the following value:
> 1. none
> 2. pause
> 3. poweroff
> 4. reset
>
> The action for each value when the guest is panicked:
> 1. none: emit QEVENT_GUEST_PANICKED only
> 2. pause: emit QEVENT_GUEST_PANICKED and pause the gue
* H. Peter Anvin wrote:
> On 07/01/2012 08:05 AM, Michael S. Tsirkin wrote:
> >On UP i386, when APIC is disabled
> ># CONFIG_X86_UP_APIC is not set
> ># CONFIG_PCI_IOAPIC is not set
> >
> >code looking at apicdrivers never has any effect but it
> >still gets compiled in. In particular, this caus
On 2012-07-06 12:50, Wen Congyang wrote:
> At 07/06/2012 06:25 PM, Jan Kiszka Wrote:
>> On 2012-07-06 11:38, Wen Congyang wrote:
>>> Signed-off-by: Wen Congyang
>>
>> Which kvm.git hash is this referring? Please state this to avoid that we
>> are merging support for kernel features that are still
On Thu, Jul 05, 2012 at 09:37:00AM -0400, Prarit Bhargava wrote:
>
>
> On 07/05/2012 09:26 AM, Avi Kivity wrote:
> > Please copy at least kvm@vger.kernel.org, and preferably Marcelo as well
> > (the other kvm co-maintainer).
> >
> >
>
> While debugging I noticed that unlike all the other hyper
On Fri, Jul 06, 2012 at 01:13:14PM +0200, Ingo Molnar wrote:
>
> * H. Peter Anvin wrote:
>
> > On 07/01/2012 08:05 AM, Michael S. Tsirkin wrote:
> > >On UP i386, when APIC is disabled
> > ># CONFIG_X86_UP_APIC is not set
> > ># CONFIG_PCI_IOAPIC is not set
> > >
> > >code looking at apicdrivers
On 07/06/12 12:09, Hans de Goede wrote:
> Here are USB 2 bug-fixes, please also cherry-pick these into the
> stable-1.1 branch, esp. the second one as that fixes an easily triggerable
> assert.
>
> Note these patches are against 1.1.0, not against master, but they are
> relevant
> for, and should
On 28.06.2012, at 08:17, Bharat Bhushan wrote:
> This patch adds the watchdog emulation in KVM. The watchdog
> emulation is enabled by KVM_ENABLE_CAP(KVM_CAP_PPC_WDT) ioctl.
> The kernel timer are used for watchdog emulation and emulates
> h/w watchdog state machine. On watchdog timer expiry, it
On Fri, 2012-07-06 at 15:42 +0800, Xiao Guangrong wrote:
> On 07/06/2012 05:50 AM, Andrew Theurer wrote:
> > I, and I expect others, have a keen interest in knowing how often we
> > exit for PLE, and also how often that includes a yielding to another
> > vcpu. The following adds two more counters
On Fri, 2012-07-06 at 02:13 -0700, Nicholas A. Bellinger wrote:
> On Fri, 2012-07-06 at 09:43 +0400, James Bottomley wrote:
> > On Thu, 2012-07-05 at 20:01 -0700, Nicholas A. Bellinger wrote:
> >
> > > So I'm pretty sure this discrepancy is attributed to the small block
> > > random I/O bottleneck
* Marcelo Tosatti wrote:
> On Fri, Jul 06, 2012 at 01:13:14PM +0200, Ingo Molnar wrote:
> >
> > * H. Peter Anvin wrote:
> >
> > > On 07/01/2012 08:05 AM, Michael S. Tsirkin wrote:
> > > >On UP i386, when APIC is disabled
> > > ># CONFIG_X86_UP_APIC is not set
> > > ># CONFIG_PCI_IOAPIC is not
Commit 0f588df8b3688b00e77aabaa32e26ece5f19bd39, added code
to ehci_wakeup to kick the async schedule on wakeup, but the else
was positioned wrong making it trigger for devices which are routed
to the companion rather then to the ehci controller itself.
This patch fixes this. Note that the "progra
On 28.06.2012, at 07:37, Bharat Bhushan wrote:
> rfci instruction and CSRR0/1 registers are emulated.
>
> Signed-off-by: Scott Wood
> Signed-off-by: Stuart Yoder
> Signed-off-by: Bharat Bhushan
Thanks, applied to kvm-ppc-next.
Alex
--
To unsubscribe from this list: send the line "unsubscr
On 25.06.2012, at 14:26, Mihai Caraman wrote:
> tlbilxva emulation was using an u32 variable for guest effective address.
> Replace it with gva_t type to handle 64-bit guests.
>
> Signed-off-by: Mihai Caraman
Thanks, applied to kvm-ppc-next.
Alex
--
To unsubscribe from this list: send the l
From: "Daniel P. Berrange"
The following commit
commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d
Author: Jan Kiszka
Date: Fri Mar 2 10:30:43 2012 +0100
qemu-kvm: Use machine options to configure qemu-kvm defaults
Upstream is moving towards this mechanism, so start using it in q
On 2012-07-06 17:41, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> The following commit
>
> commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d
> Author: Jan Kiszka
> Date: Fri Mar 2 10:30:43 2012 +0100
>
> qemu-kvm: Use machine options to configure qemu-kvm defaults
>
>
> From: Kun Wang [mailto:wang...@cn.ibm.com]
> Sent: Friday, July 06, 2012 5:07 PM
> To: Caraman Mihai Claudiu-B02008
> Cc: ag...@suse.de; kvm@vger.kernel.org; kvm-...@vger.kernel.org;
> kvm-ppc-ow...@vger.kernel.org
> Subject: Re: [PATCH] KVM: PPC: bookehv: Add ESR flag to Data Storage Interrupt
qemu-kvm-specific machine defaults were missing for pc-0.15 to pc-1.1.
Then Daniel noted that --disable-kvm caused problems as the generated
binaries would be unable to run. As we are at it, we can drop the
kernel_irqchip=on that is now enable by default in upstream.
CC: Daniel P. Berrange
Signed
Replace the home-brewed qdev property for PCI host addresses with the
new upstream version.
Signed-off-by: Jan Kiszka
---
hw/device-assignment.c | 64 ---
hw/pci.c | 77
hw/pci.h
On 07/06/2012 12:42 AM, Jason Wang wrote:
I'm not expert of tcp, but looks like the changes are reasonable:
- we can do full-sized TSO check in tcp_tso_should_defer() only for
westwood, according to tcp westwood
- run tcp_tso_should_defer for tso_segs = 1 when tso is enabled.
I'm sure Eric and
On 2012-06-24 16:08, Jan Kiszka wrote:
> On 2012-06-24 10:49, Avi Kivity wrote:
>> On 06/23/2012 02:45 PM, Jan Kiszka wrote:
>>>
>>> Hmm, we may need the iothread lock around cpu_set_apic_tpr for
>>> !kvm_irqchip_in_kernel(). And as we are at it, apic_base manipulation
>>> can be but there as well.
On 07/06/2012 09:22 PM, Andrew Theurer wrote:
> On Fri, 2012-07-06 at 15:42 +0800, Xiao Guangrong wrote:
>> On 07/06/2012 05:50 AM, Andrew Theurer wrote:
>>> I, and I expect others, have a keen interest in knowing how often we
>>> exit for PLE, and also how often that includes a yielding to another
On 2012-07-06 19:16, Jan Kiszka wrote:
> On 2012-06-24 16:08, Jan Kiszka wrote:
>> On 2012-06-24 10:49, Avi Kivity wrote:
>>> On 06/23/2012 02:45 PM, Jan Kiszka wrote:
Hmm, we may need the iothread lock around cpu_set_apic_tpr for
!kvm_irqchip_in_kernel(). And as we are at it, apic_b
On Tue, Jun 19, 2012 at 04:51:04PM -0400, Rik van Riel wrote:
> On Wed, 20 Jun 2012 01:50:50 +0530
> Raghavendra K T wrote:
>
> >
> > In ple handler code, last_boosted_vcpu (lbv) variable is
> > serving as reference point to start when we enter.
>
> > Also statistical analysis (below) is showin
On Fri, Jul 06, 2012 at 06:21:06PM +0200, Jan Kiszka wrote:
> qemu-kvm-specific machine defaults were missing for pc-0.15 to pc-1.1.
> Then Daniel noted that --disable-kvm caused problems as the generated
> binaries would be unable to run. As we are at it, we can drop the
> kernel_irqchip=on that i
On 07/06/2012 07:27 AM, Marcelo Tosatti wrote:
> On Thu, Jul 05, 2012 at 09:37:00AM -0400, Prarit Bhargava wrote:
>>
>>
>> On 07/05/2012 09:26 AM, Avi Kivity wrote:
>>> Please copy at least kvm@vger.kernel.org, and preferably Marcelo as well
>>> (the other kvm co-maintainer).
>>>
>>>
>>
>> While
On Fri, 2012-07-06 at 17:49 +0400, James Bottomley wrote:
> On Fri, 2012-07-06 at 02:13 -0700, Nicholas A. Bellinger wrote:
> > On Fri, 2012-07-06 at 09:43 +0400, James Bottomley wrote:
> > > On Thu, 2012-07-05 at 20:01 -0700, Nicholas A. Bellinger wrote:
> > >
> > > > This bottleneck has been
On Sat, 2012-07-07 at 01:40 +0800, Xiao Guangrong wrote:
> On 07/06/2012 09:22 PM, Andrew Theurer wrote:
> > On Fri, 2012-07-06 at 15:42 +0800, Xiao Guangrong wrote:
> >> On 07/06/2012 05:50 AM, Andrew Theurer wrote:
> >>> I, and I expect others, have a keen interest in knowing how often we
> >>> e
On 17.06.2012 17:14, Avi Kivity wrote:
> On 06/17/2012 04:06 PM, Blue Swirl wrote:
>
>>> strtosz() is much too general. We could do it in vl.c without trouble.
>>> However, it takes away our ability to emulate a "640k should be enough
>>> for everyone" machine.
>>
>> Then how about current max o
From: Nicholas Bellinger
This patch changes virtio-scsi to use a new virtio_driver->scan() callback
so that scsi_scan_host() can be properly invoked once virtio_dev_probe() has
set add_status(dev, VIRTIO_CONFIG_S_DRIVER_OK) to signal active virtio-ring
operation, instead of from within virtscsi_p
Hi James,
Please consider picking this one up for your next scsi-rc-fixes PULL,
and it's CC'ed to stable following Paolo's request.
Thank you,
--nab
On Fri, 2012-07-06 at 20:15 +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> This patch changes virtio-scsi to use a new virti
On Fri, 6 Jul 2012, James Bottomley wrote:
> What people might pay attention to is evidence that there's a problem in
> 3.5-rc6 (without any OFED crap). If you're not going to bother
> investigating, it has to be in an environment they can reproduce (so
> ordinary hardware, not infiniband) otherw
On Fri, 2012-07-06 at 15:30 -0500, Christoph Lameter wrote:
> On Fri, 6 Jul 2012, James Bottomley wrote:
>
> > What people might pay attention to is evidence that there's a problem in
> > 3.5-rc6 (without any OFED crap). If you're not going to bother
> > investigating, it has to be in an environm
> -Original Message-
> From: Benjamin Herrenschmidt [mailto:b...@kernel.crashing.org]
> Sent: Thursday, July 05, 2012 1:26 AM
> To: Alexander Graf
> Cc: Caraman Mihai Claudiu-B02008; ; KVM list;
> linuxppc-dev; qemu-...@nongnu.org List
> Subject: Re: [Qemu-ppc] [RFC PATCH 12/17] PowerPC: bo
> -Original Message-
> From: Linuxppc-dev [mailto:linuxppc-dev-
> bounces+mihai.caraman=freescale@lists.ozlabs.org] On Behalf Of
> Benjamin Herrenschmidt
> Sent: Thursday, July 05, 2012 1:21 AM
> To: Alexander Graf
> Cc: qemu-...@nongnu.org List; Caraman Mihai Claudiu-B02008; linuxppc-d
On 07.07.2012, at 00:33, Caraman Mihai Claudiu-B02008 wrote:
>> -Original Message-
>> From: Benjamin Herrenschmidt [mailto:b...@kernel.crashing.org]
>> Sent: Thursday, July 05, 2012 1:26 AM
>> To: Alexander Graf
>> Cc: Caraman Mihai Claudiu-B02008; ; KVM list;
>> linuxppc-dev; qemu-...@no
On 07/06/2012 08:17 AM, Alexander Graf wrote:
> On 28.06.2012, at 08:17, Bharat Bhushan wrote:
>> +/*
>> + * The timer system can almost deal with LONG_MAX timeouts, except that
>> + * when you get very close to LONG_MAX, the slack added can cause overflow.
>> + *
>> + * LONG_MAX/2 is a conservativ
74 matches
Mail list logo
