WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: Using pciback to dynamically bind/unbind primary display

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Using pciback to dynamically bind/unbind primary display driver: lost console, help
From: Ben Himberg <bhimberg@xxxxxxxxx>
Date: Fri, 28 Oct 2011 22:14:05 -0400
Cc:
Delivery-date: Fri, 28 Oct 2011 19:15:25 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=75GindWoLV2BRbqMSUAYtpJQYIU0scAt0p6ZAIPX8t0=; b=vEToFoMISM/ippJAnXrbrE7oIBn7YOINZTwJKrZ70HLDS1vUh3Pf961kg0Vig9JqcD XSXxDUBFKfl1gkZ7OIXzjqSkO+JeVvRXpmULH+ab9W/nsZTNU+o2XfHicZJnXxw11ec3 qPyt/0lZdIujNvl3mZ6DVHDaSRF/lZMwWzmfM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CABsZVk8apSgwgG=H-wJR9eZ47b5jZBzfeZwbpJ2gVkg0wkkpKQ@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <CABsZVk8apSgwgG=H-wJR9eZ47b5jZBzfeZwbpJ2gVkg0wkkpKQ@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Turns out I passed "dynpm" to radeon/power_profile instead of radeon/power_method and it crashed atom bios (kept locking, timing out in the error log).  Works fine now.  How do I control, on the fly, where kernel output goes though?

On Fri, Oct 28, 2011 at 9:35 PM, Ben Himberg <bhimberg@xxxxxxxxx> wrote:
On Debain 3.1.0-rc7, Radeon 6870 and Xen 4.1 (no patches)

I used

echo -n 0000:01:00.0 > /sys/bus/pci/drivers/radeon/unbind
echo -n 0000:01:00.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:01:00.0 > /sys/bus/pci/drivers/pciback/bind

to move my primary display adapter (01:00.0) to pciback for domU use.  The display, as expected, turned off.  I had enabled ssh to do this, and have access to the system still.  I then used

echo -n 0000:01:00.0 > /sys/bus/pci/drivers/pciback/unbind
echo -n 0000:01:00.0 > /sys/bus/pci/drivers/radeon/bind

to pass it back to dom0 at which point the display turned back on.  Thinking all was well, I made a script to do the above and executed it (with a sleep of 10 seconds after the first bind) at which point I lost the display, as expected, but it didn't come back.  I then logged in through ssh and find that the radeon driver is bound to 01:00.0, but still no display.

I think I need to tell the console to output to the radeon driver, but I have no idea how and a google search is proving fruitless.  Any help?  I've also noticed that unbinding/binding the radeon driver is now (it wasn't initially) very slow to respond.

Thanks!

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users