xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Matěja" <pavel@netsafe.cz>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: ATI/AMD VGA passthru report
Date: Wed, 9 May 2012 20:25:56 +0200	[thread overview]
Message-ID: <201205092025.57037.pavel@netsafe.cz> (raw)
In-Reply-To: <20120509174426.GD9094@phenom.dumpdata.com>

On Wed 9. of May 2012 19:44:26 you wrote:
> > Hi again!
> > I did first tests with xen-unstable and the #testing kernel.
> > 
> > Windows showed blue screen during boot with xm toolstack.
> > 
> > But I had luck with xl. Windows booted succesfully so I ran the
> > experience index tests:
> > 
> > kernel:	2.6.32.57	#testing
> > CPU		7,4		7,4
> > RAM		7,4		5,5
> > Aero		7,1		7,1
> > Gr.card	7,1		7,1
> > Disk		7,3		7,5
> 
> So the issue was that 'xm' didn't work but 'xl' did?

In fact it's:
2.6.32.57 and old xen-unstable build (May 2011) with xm toolstack,
#testing and latest xen-unstable with xl toolstack.
No other combinations are working.

> > I tried to run some games as well but the feeling is much worse compared
> > to older configuration. Like lags..
> 
> Do the lags disappear if you pin the vCPUs?

Do you mean for Dom0 or DomU?
I already pin all vCPUs for DomUs. I can try to dedicate one to xen and rest 
to Windows.
But current config (Phenom II X6) was able to run 3 cores for first Windows, 
other 3 cores for second Windows and Dom0 had 2 unpinned cores. All was 
smooth.
Even 2 cores per instance fro three Windows instances were just fine.
Right now I'm trying just one Windows instance with all cores pinned.

> > Are there some older branches which are supposed to work?
> 
> There is not a specific branch per say. There are some auxillary branches
> with patches that enable this and that. So what might work is
> to use my #linux-next branch and merge both devel/misc and devel/ioperm
> in and see what happens. If I get some time today I will try that and
> stick it as tag.
> 
> > I tried xen-4.1.3-rc1 with #testing kernel but it just freezes after
> > while even with Dom0 running. Only sys-rq worked.
> 
> Oh no!

On no to my english.
;)
It should be: system freezes after while even when only Dom0 is running.
How can I debug this? All I can do is reading sysrq messages but I see no real 
dumps in serial console. Like:
..
SysRq : Show Regs
SysRq : Show Blocked State
SysRq : Show clockevent devices & pending hrtimers (no others)
..

> > I have second slightly newer system too so I'll retest that one later.

Sorry, no time yet. I just tried same thing I did on old system and result is 
instant reboot somewhere after NIC detection. Maybe the fs is gone somehow..
I have to switch the serial card to debug that one.
-- 
Pavel Mateja

  reply	other threads:[~2012-05-09 18:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 11:45 ATI/AMD VGA passthru report Pavel Matěja
2012-05-07 13:46 ` Pavel Matěja
2012-05-07 17:31 ` Konrad Rzeszutek Wilk
2012-05-07 23:10   ` Pavel Mateja
2012-05-07 23:07     ` Konrad Rzeszutek Wilk
2012-05-08 11:12       ` Pavel Matěja
2012-05-09 17:44         ` Konrad Rzeszutek Wilk
2012-05-09 18:25           ` Pavel Matěja [this message]
2012-05-09 18:59           ` Pavel Matěja
2012-05-09 19:18             ` djmagee

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=201205092025.57037.pavel@netsafe.cz \
    --to=pavel@netsafe.cz \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).