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

Re: [XenPPC] [PATCH] [RFC] Fix xenminicom optimizations to work for modu

To: Jerone Young <jyoung5@xxxxxxxxxx>
Subject: Re: [XenPPC] [PATCH] [RFC] Fix xenminicom optimizations to work for module
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Wed, 10 Jan 2007 13:15:57 -0600
Cc: Xen-ppc <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 10 Jan 2007 11:15:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1168455583.5784.36.camel@thinkpad>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <1168451469.5784.28.camel@thinkpad> <1168454738.8521.46.camel@basalt> <1168455583.5784.36.camel@thinkpad>
Reply-to: Hollis Blanchard <hollisb@xxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2007-01-10 at 12:59 -0600, Jerone Young wrote:
> 
> > > @@ -286,7 +286,7 @@ int HYPERVISOR_grant_table_op(unsigned i
> > >                 return -ENOSYS;
> > >         }
> > >
> > > -       desc = xencomm_create_inline(op);
> > > +       desc = xencomm_create_inline(op, 0);
> > >
> > >         ret =
> plpar_hcall_norets(XEN_MARK(__HYPERVISOR_grant_table_op), cmd,
> > >                                  desc, count);
> >
> > Throughout your entire patch you're using a size of 0. That can't be
> > right.
> 
> Glad you pointed this out. Actually, in these cases I use 0 (why the
> patch isn't perfect) to ensure that we are not returned a NULL pointer.
> Since this is code that has just been added. Since the check is not
> needed in theses cases, but perhaps it will always pass and this is not
> going to be a worry.

As we discussed in person, it certainly is a worry. The check should not
always pass, and we do need to test for failure.

-- 
Hollis Blanchard
IBM Linux Technology Center


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

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