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-devel

Re: [Xen-devel] Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0
From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Date: Wed, 3 Aug 2011 19:31:04 +0200
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 03 Aug 2011 10:32:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110803155358.GA21704@xxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Eikelenboom IT services
References: <1006432958.20110803131824@xxxxxxxxxxxxxx> <20110803134129.GF26828@xxxxxxxxxxxx> <20110803135151.GB29501@xxxxxxxxxxxx> <306513218.20110803170524@xxxxxxxxxxxxxx> <20110803155358.GA21704@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Wednesday, August 3, 2011, 5:53:58 PM, you wrote:

> On Wed, Aug 03, 2011 at 05:05:24PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad,
>> 
>> Thx, after applying those patches it boots as dom0 and xen-pciback seems to 
>> work as well from my first tests.

> Could you reply to that email thread with 'Tested-by: ' if it is not too much 
> trouble?

I will :-)

>> The compile problems reported in my earlier mail are still present (related 
>> to tracing and i think jeremy's patches).
>> 
>> Something that catched my eye when doing a make menuconfig:
>>           <*>   Xen virtual block device support
>>           <*>   Block-device backend driver
>> 
>> I think the backend description should also start with "Xen" as all xen 
>> specific drivers do ?

> I've gotten this patch queued up (if you think of a better name or if you 
> think
> the description could use some re-wording - please do provide some ideas):

Can't think of a better one :-)

> commit 4beb84ffeacbf8df21b41ca8c05d099e19c579a3
> Author: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> Date:   Wed Aug 3 11:12:17 2011 -0400

>     xen/blkback: Make description more obvious.
>     
>     With the frontend having Xen but the backend not, it just looks odd:
>     
>       <*>   Xen virtual block device support
>       <*>   Block-device backend driver
>     
>     Fix it to have the 'Xen' in front of it.
>     
>     Reported-by: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
>     Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>

> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 717d6e4..a89ebf1 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -471,7 +471,7 @@ config XEN_BLKDEV_FRONTEND
>           in another domain which drives the actual block device.
>  
>  config XEN_BLKDEV_BACKEND
> -       tristate "Block-device backend driver"
> +       tristate "Xen block-device backend driver"
>         depends on XEN_BACKEND
>         help
>           The block-device backend driver allows the kernel to export its



-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx


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

<Prev in Thread] Current Thread [Next in Thread>