xen-devel

[Top] [All Lists]

Re: [Xen-devel] [PATCH] libxc: fix lock_pages()/unlock_pages()

from [Masaki Kanno]

[Permanent Link][Original]

To:	Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	Re: [Xen-devel] [PATCH] libxc: fix lock_pages()/unlock_pages()
From:	Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date:	Mon, 01 Oct 2007 21:20:41 +0900
Delivery-date:	Mon, 01 Oct 2007 05:21:27 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<20071001110457.GB15863%yamahata@xxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<20071001110457.GB15863%yamahata@xxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Hi Isaku,

Thanks for your patch. 

I was encountering xm dump-core command error with latest xen-unstable. 
The command error was as follows. 

 # xm list
 Name                                        ID   Mem VCPUs      State   Time(s)
 Domain-0                                     0   747     2     r-----     63.2
 vm1                                          1   256     1     r-----    111.1
 # xm dump-core vm1
 Dumping core of domain: vm1 ...
 Error: Failed to dump core: (1, 'Internal error', 'No VCPU context could be 
grabbed (14 = Bad address)')
 Usage: xm dump-core [-L|--live] [-C|--crash] <Domain> [Filename]
 
 Dump core for a specific domain.
   -L, --live                     Dump core without pausing the domain
   -C, --crash                    Crash domain after dumping core


But, the command error was resolved by your patch. 

Best regards,
 Kan

Mon, 1 Oct 2007 20:04:57 +0900, Isaku Yamahata wrote:

>fix lock_pages()/unlock_pages(). The resion is sometimes wrongly calculated.
>It results in unexpected hypercall failure.
>
>-- 
>yamahata
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel


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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH] libxc: fix lock_pages()/unlock_pages(), Isaku Yamahata Re: [Xen-devel] [PATCH] libxc: fix lock_pages()/unlock_pages(), Masaki Kanno <=

Previous by Date:	Re: [Xen-devel] early crash with xen-3.1.0 and auto_translated_physmap, Keir Fraser
Next by Date:	Re: [Xen-devel] Reporting a traceback, Marc Patino Gómez
Previous by Thread:	[Xen-devel] [PATCH] libxc: fix lock_pages()/unlock_pages(), Isaku Yamahata
Next by Thread:	Re: [Xen-devel] early crash with xen-3.1.0 and auto_translated_physmap, Daniel Stodden
Indexes:	[Date] [Thread] [Top] [All Lists]