From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Simon Martin <furryfuttock@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Grant access to more than one dom
Date: Thu, 08 May 2014 15:01:01 -0400 [thread overview]
Message-ID: <536BD46D.5050106@tycho.nsa.gov> (raw)
In-Reply-To: <1746801210.20140508114712@gmail.com>
On 05/08/2014 11:47 AM, Simon Martin wrote:
> Hi Daniel.
>
>> I'll carry on then. When I have it working and tested I'll send it to
>> you so you can have a look. Once everyone is happy I'll see about
>> pushing it to a kernel maintainer.
>
> After being sidetracked into other more boring projects I have now
> almost completed this change, however I have some questions. I'm
> pretty certain that I must be missing something here.
>
> For the moment I am only looking at gntalloc.c as it is the one I
> need.
>
> In the add_grefs function you create a couple of list structures
> (queue_gref and queue_file) and then splice these onto the end of the
> gref_list and gntalloc_file_private_data.list lists. However I'm not
> really sure what you are doing here. Can you explain please. The
> problems I see are:
>
> 1.- queue_gref and queue_file are declared on the stack, however they
> are then appended to the lists with no memory allocation whatsoever.
> What are you expecting to happen here?
>
> 2.- queue_gref and queue_file are just list structs, i.e. they have
> no payload, they are not part of an encapsulating struct, so again,
> what are you expecting to happen here?
>
> Regards.
The add_grefs function strings the allocated gntalloc_gref structures onto
two linked lists: the list heads are local, but are only used temporarily.
If the operation is successful, the list_splice_tail calls wire up the
linked lists to permanent structures on the heap; if unsuccessful, they
are used to clean up.
--
Daniel De Graaf
National Security Agency
next prev parent reply other threads:[~2014-05-08 19:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 14:58 Grant access to more than one dom Simon Martin
2014-04-17 15:03 ` Ian Campbell
2014-04-17 15:07 ` Simon Martin
2014-04-17 15:38 ` Simon Martin
2014-04-17 16:14 ` Ian Campbell
2014-04-17 16:57 ` Simon Martin
2014-04-17 17:16 ` Daniel De Graaf
2014-04-17 18:06 ` Simon Martin
2014-04-25 12:12 ` Simon Martin
2014-04-25 12:16 ` Ian Campbell
2014-04-25 12:18 ` Simon Martin
2014-04-25 12:28 ` Ian Campbell
2014-05-08 15:47 ` Simon Martin
2014-05-08 19:01 ` Daniel De Graaf [this message]
2014-05-08 20:03 ` Simon Martin
2014-05-08 20:23 ` Daniel De Graaf
2014-05-09 14:00 ` Simon Martin
2014-06-05 16:10 ` Simon Martin
2014-06-06 9:51 ` Ian Campbell
2014-06-06 21:02 ` Daniel De Graaf
2014-06-09 15:53 ` Simon Martin
2014-06-09 17:15 ` Daniel De Graaf
2014-06-10 18:48 ` Simon Martin
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=536BD46D.5050106@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=Ian.Campbell@citrix.com \
--cc=furryfuttock@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.