Displaying 11 results from an estimated 11 matches for "presumarili".
Did you mean:
presumarily
2013 Dec 02
6
GTX 760 passed through
Hello,
I''ve successfully passed a unmodified GTX 760 to Win7 x64. It involved some
driver patching on the client side but I''m close to getting the required
steps on the server side, too. Are there any legal issues that might arise
from releasing a patch?
Bob
[image: Inline image 1]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
2014 Feb 26
2
[PATCH RFC v5 4/8] pvqspinlock, x86: Allow unfair spinlock in a real PV environment
On Wed, Feb 26, 2014 at 10:14:24AM -0500, Waiman Long wrote:
> Locking is always an issue in a virtualized environment as the virtual
> CPU that is waiting on a lock may get scheduled out and hence block
> any progress in lock acquisition even when the lock has been freed.
>
> One solution to this problem is to allow unfair lock in a
> para-virtualized environment. In this case,
2014 Feb 26
2
[PATCH RFC v5 4/8] pvqspinlock, x86: Allow unfair spinlock in a real PV environment
On Wed, Feb 26, 2014 at 10:14:24AM -0500, Waiman Long wrote:
> Locking is always an issue in a virtualized environment as the virtual
> CPU that is waiting on a lock may get scheduled out and hence block
> any progress in lock acquisition even when the lock has been freed.
>
> One solution to this problem is to allow unfair lock in a
> para-virtualized environment. In this case,
2013 Aug 27
4
Is: Xen 4.2 and using 'xl' to save/restore is buggy with PVHVM Linux guests (v3.10 and v3.11 and presumarily earlier as well). Works with Xen 4.3 and Xen 4.4. Was:Re: FAILURE 3.11.0-rc7upstream(x86_64) 3.11.0-rc7upstream(i386)\: 2013-08-26 (tst001)
Hey,
I have a nighly build/test system that boots various machines with
upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable.
After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'')
has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'')
the PVHVM
2014 Feb 28
0
[PATCH RFC v5 4/8] pvqspinlock, x86: Allow unfair spinlock in a real PV environment
On 02/26/2014 12:07 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Feb 26, 2014 at 10:14:24AM -0500, Waiman Long wrote:
>> Locking is always an issue in a virtualized environment as the virtual
>> CPU that is waiting on a lock may get scheduled out and hence block
>> any progress in lock acquisition even when the lock has been freed.
>>
>> One solution to this problem
2014 Sep 30
1
[PATCH v5 2/3] virtio_pci: Use the DMA API for virtqueues when possible
On Tue, Sep 30, 2014 at 10:53 AM, Konrad Rzeszutek Wilk
<konrad.wilk at oracle.com> wrote:
>> x86 will be worse than PPC, too: the special case needed to support
>> QEMU 2.2 with IOMMU and virtio enabled with a Xen guest will be fairly
>> large and disgusting and will only exist to support something that IMO
>> should never have existed in the first place.
>
>
2014 Sep 30
1
[PATCH v5 2/3] virtio_pci: Use the DMA API for virtqueues when possible
On Tue, Sep 30, 2014 at 10:53 AM, Konrad Rzeszutek Wilk
<konrad.wilk at oracle.com> wrote:
>> x86 will be worse than PPC, too: the special case needed to support
>> QEMU 2.2 with IOMMU and virtio enabled with a Xen guest will be fairly
>> large and disgusting and will only exist to support something that IMO
>> should never have existed in the first place.
>
>
2012 Feb 17
6
Reboots and Panics(4.1.2/4.2-unstable)
Environment:
ASRock Z86 Extreme4 - Intel i5 2500
http://www.asrock.com/mb/overview.asp?Model=Z68%20Extreme4
I have installed the latest UEFI patch(1.70) and all tests were run from a
reset of everything to default. I have tested with both Ubuntu 11.10 and
Fedora 16 and get the same results on both, including building xen
4.2-unstable. I bought this particular MB because it had a know working
vt-d
2013 Jul 23
73
Bug: Limitation of <=2GB RAM in domU persists with 4.3.0
I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU
passthrough without crashes. Unfortunately, the same crashes still
happen. Massive frame buffer corruption on domU before it locks up
solid. It seems the PCI memory stomp is still happening.
I am using qemu-dm, as I did on Xen 4.2.x.
So whatever fix for this went into 4.3.0 didn''t fix it for me.
Passing less than 2GB
2014 Feb 26
22
[PATCH v5 0/8] qspinlock: a 4-byte queue spinlock with PV support
v4->v5:
- Move the optimized 2-task contending code to the generic file to
enable more architectures to use it without code duplication.
- Address some of the style-related comments by PeterZ.
- Allow the use of unfair queue spinlock in a real para-virtualized
execution environment.
- Add para-virtualization support to the qspinlock code by ensuring
that the lock holder and queue
2014 Feb 26
22
[PATCH v5 0/8] qspinlock: a 4-byte queue spinlock with PV support
v4->v5:
- Move the optimized 2-task contending code to the generic file to
enable more architectures to use it without code duplication.
- Address some of the style-related comments by PeterZ.
- Allow the use of unfair queue spinlock in a real para-virtualized
execution environment.
- Add para-virtualization support to the qspinlock code by ensuring
that the lock holder and queue