All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Bege <therion@ninth-art.de>
To: Gordan Bobic <gordan@bobich.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Fwd: Re:  Xen 4.3 / 4.4 - concurrent APIs, VGA Passthru
Date: Mon, 18 Aug 2014 17:26:24 +0200	[thread overview]
Message-ID: <53F21B20.90108@ninth-art.de> (raw)
In-Reply-To: <53DF41E3.9000406@bobich.net>

Hi

I simply wanted to tell my tale about the outcome of my experiments,
I was occupied with certain other things (including exchanging some
zpool's).
For now I run an Vista x64 and it works pretty well, I never got the
gplpv drivers running on
acceptable levels (they are still quite slow) so I decided to pass
onboard controller, sound and usb3.
This decission seemed to be a wise one and everything works great as
expected, the problem with gplpv
well it might also be a result of my volume scheme since I only run ZFS
- now an raidz1 (on enterprise disks though).
I also replaced the nvidia drivers from 331.65 to 337.88 - this revision
gave me a lot more performance but I can remember I had this issue on
native Windows too.

So after a lot of testing, pain, time consuming days (and nights) its
really working great - not perfect maybe.
My next goal is to dedicate an SSD for that system volume, maybe try
Win7 again as well -
also I'd like to get an GTX690 and hardmod it so I get a lot more speed...

regards,
Georg

Am 04.08.2014 10:18, schrieb Gordan Bobic:
> On 08/03/2014 11:09 AM, Georg Bege wrote:
>>
>> Am 03.08.2014 11:49, schrieb Gordan Bobic:
>>> On 08/02/2014 11:49 AM, Georg Bege wrote:
>>>> Hello again
>>>>
>>>> Well so far I can now tell, I tested it on WinXP x64 quite a lot
>>>> - most things are working.
>>>> Including AAA games like Witcher 2, I didnt try a very memory
>>>> consuming
>>>> game yet.
>>>> But I dont really think that I have the same bug you are refering to -
>>>> in WinXP x64 the /PATCHTPR boot flag did help greatly, it really
>>>> boosted
>>>> the performance to near native.
>>>
>>> What does this flag do? Googling for it found no results.
>> See:
>> http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00254.html
>>
>>
>> But now I came to the conclusion that I dont have the same issue with
>> Win7 at all (see last email).
>
> This reminds me - I had issues with the latest GPLPV drivers on
> Windows 7. The installer would just sit there and never complete,
> which also, IIRC, left the VM OS in a dodgy state. So I nstalled the
> same version (version number, not package, obviously) I've been
> running on XP64 for ages (11.0.372) and that worked fine.
>
>>>> I dont think I encountered any memory usage, used like applications
>>>> consuming the first 4GB of the DomU.
>>>
>>> I am inclined to agree, you aren't hitting the same problem.
>>>
>>>> Im trying to figure what to do for Windows 7, its working good too -
>>>> even with VGA Passthrough,
>>>> but its almost always consuming 33%-80% CPU usage for no reason...
>>>
>>> Can you check from within the domU which process is eating CPU? Or are
>>> you saying that with Windows 7 inside your domU task manager is
>>> showing 0% CPU usage but xentop is showing 33-80% CPU usage?
>> I cant check, as states in the last email it must be about interrupts or
>> power saving states - it only happens when I pass in the GFX.
>> Without this the CPU is just idling on 0% inside the DomU.
>
> Funnily enough, I'm seeing something similar in dom0 when I use a
> GT630 card, but not when I'm using an 8800GT or Q2K. With the GT630,
> Xorg locks up immediately, eating 100% of CPU with ksoftirqd eating
> another 100% of CPU. X process is unkillable so the only way to
> recover is to reboot the machine. The same GT630 runs fine in another
> machine so I'm reasonably sure that's not the problem. So it _could_
> be a similar obscure bug in the Nvidia driver.
>
> Have you tried 331.93? That's the driver I'm using.
>
>
> Gordan

  parent reply	other threads:[~2014-08-18 15:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53D5C00E.5040706@ninth-art.de>
2014-07-28 14:10 ` Fwd: Re: Xen 4.3 / 4.4 - concurrent APIs, VGA Passthru Georg Bege
2014-07-28 14:34   ` jacek burghardt
2014-07-28 15:01   ` Gordan Bobic
     [not found]     ` <53D6F500.1010806@ninth-art.de>
     [not found]       ` <53D748DC.10209@bobich.net>
     [not found]         ` <53D74F9E.6010508@ninth-art.de>
     [not found]           ` <bb4d5eb4f453e5596f696eb93c3f7df5@mail.shatteredsilicon.net>
2014-07-29 11:52             ` Georg Bege
2014-07-29 12:22               ` Gordan Bobic
2014-08-02 10:49                 ` Georg Bege
2014-08-03  9:49                   ` Gordan Bobic
     [not found]                     ` <53DE0A73.9040304@ninth-art.de>
2014-08-03 10:20                       ` Fwd: " Georg Bege
2014-08-04  8:18                       ` Gordan Bobic
2014-08-04 19:30                         ` Georg Bege
2014-08-18 15:26                         ` Georg Bege [this message]
2014-08-18 15:45                           ` Gordan Bobic
2014-08-18 21:13                             ` Richie
2014-08-19 10:31                               ` Gordan Bobic
2014-08-03  9:57                   ` James Harper
2014-08-03  1:09             ` Georg Bege
2014-08-03  9:40               ` Gordan Bobic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53F21B20.90108@ninth-art.de \
    --to=therion@ninth-art.de \
    --cc=gordan@bobich.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.