From: "Markus Groß" <gross@univention.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: libxc: correctly unmap pages after core-dumping a pv guest
Date: Tue, 24 May 2011 18:22:55 +0200 [thread overview]
Message-ID: <20110524182255.18755u24gwhgyd8g@mail.univention.de> (raw)
In-Reply-To: <19931.51607.411678.708897@mariner.uk.xensource.com>
Quoting Ian Jackson <Ian.Jackson@eu.citrix.com>:
> Markus Groß writes ("[Xen-devel] libxc: correctly unmap pages after
> core-dumping a pv guest"):
>> But to unmap the pages later, the dinfo->p2m_size has to be set accordingly.
>> This was not done, instead a variable named p2m_size was set.
>> This way P2M_FL_ENTRIES was always zero and the pages were left mapped.
>>
>> The following patch fixes this.
>
> Thanks. The existing code here is pretty unfortunate.
>
> In xc_domain_dumpcore_via_callback where you make your change, "dinfo"
> refers to a struct domain_info_context which is local to that
> function. But in the called function xc_core_arch_map_p2m_rw, "dinfo"
> refers to another identical structure allocated locally to the small
> wrapper function xc_core_arch_map_p2m. All rather tangled.
>
> But, anyway, your change is correct so I have applied it.
>
> Next time, though, can you please be sure to add a Signed-off-by line,
> to signify your certification in accordance with the Developer's
> Certificate of Origin ? In this case I'll go ahead as it's only a
> couple of lines.
>
> Thanks,
> Ian.
Thanks, although I did repost the patch with a Signed-off-by line here:
http://lists.xensource.com/archives/html/xen-devel/2011-05/msg01469.html
Cheers,
Markus
>
> From Documentation/SubmittingPatches in the Linux kernel tree:
>
> Developer's Certificate of Origin 1.1
>
> By making a contribution to this project, I certify that:
>
> (a) The contribution was created in whole or in part by me and I
> have the right to submit it under the open source license
> indicated in the file; or
>
> (b) The contribution is based upon previous work that, to the best
> of my knowledge, is covered under an appropriate open source
> license and I have the right under that license to submit that
> work with modifications, whether created in whole or in part
> by me, under the same open source license (unless I am
> permitted to submit under a different license), as indicated
> in the file; or
>
> (c) The contribution was provided directly to me by some other
> person who certified (a), (b) or (c) and I have not modified
> it.
>
> (d) I understand and agree that this project and the contribution
> are public and that a record of the contribution (including all
> personal information I submit with it, including my sign-off) is
> maintained indefinitely and may be redistributed consistent with
> this project or the open source license(s) involved.
>
next prev parent reply other threads:[~2011-05-24 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 11:42 libxc: correctly unmap pages after core-dumping a pv guest Markus Groß
2011-05-23 12:24 ` Markus Groß
2011-05-23 12:46 ` Ian Campbell
2011-05-23 13:12 ` [PATCH] " Markus Groß
2011-05-24 15:07 ` Ian Jackson
2011-05-24 16:22 ` Markus Groß [this message]
2011-05-24 17:32 ` Ian Jackson
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=20110524182255.18755u24gwhgyd8g@mail.univention.de \
--to=gross@univention.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).