xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 00 of 12] xenpaging fixes for xen-unstable
Date: Fri, 10 Jun 2011 13:52:22 +0100	[thread overview]
Message-ID: <CA17D216.1C07E%keir.xen@gmail.com> (raw)
In-Reply-To: <20110610112733.GA17891@aepfle.de>

On 10/06/2011 12:27, "Olaf Hering" <olaf@aepfle.de> wrote:

> On Fri, Jun 10, Keir Fraser wrote:
> 
>> On 07/06/2011 14:38, "Olaf Hering" <olaf@aepfle.de> wrote:
>> 
>>> On Tue, Jun 07, Keir Fraser wrote:
>>> 
>>>> Once they're in, what is left to do? Do you need help with the in-Xen
>>>> waitqueue stuff? Do you have test cases that fail, a private patch queue,
>>>> etc?
>>> 
>>> Keir,
>>> 
>>> I have no new patches, just returned to xenpaging end of last week.
>>> A few months ago I collected my TODO list below.
>>> 
>>> One thing that I would need help with is the machine_to_phys_mapping[]
>>> handling, an attempt to fix it was reverted before the 4.1 release. See
>>> the thread in the URL below.
>> 
>> I've reapplied this as xen-unstable:23507.
> 
> Thanks Keir.
> 
> But the change breaks 32bit builds:

Thanks, fixed by xen-unstable:23509.

 -- Keir

> prelink.o: In function `populate_physmap':
> /usr/src/packages/BUILD/xen-unstable.hg-4.2.23508/xen/common/memory.c:155:
> undefined reference to `machine_to_phys_mapping_valid'
> prelink.o: In function `memory_exchange':
> /usr/src/packages/BUILD/xen-unstable.hg-4.2.23508/xen/common/memory.c:491:
> undefined reference to `machine_to_phys_mapping_valid'
> prelink.o: In function `free_heap_pages':
> /usr/src/packages/BUILD/xen-unstable.hg-4.2.23508/xen/common/page_alloc.c:544:
> undefined reference to `machine_to_phys_mapping_valid'
> prelink.o: In function `share_xen_page_with_guest':
> /usr/src/packages/BUILD/xen-unstable.hg-4.2.23508/xen/arch/x86/mm.c:440:
> undefined reference to `machine_to_phys_mapping_valid'
> prelink.o: In function `do_mmu_update':
> /usr/src/packages/BUILD/xen-unstable.hg-4.2.23508/xen/arch/x86/mm.c:3688:
> undefined reference to `machine_to_phys_mapping_valid'
> prelink.o:/usr/src/packages/BUILD/xen-unstable.hg-4.2.23508/xen/arch/x86/mm/p2
> m.c:373: more undefined references to `machine_to_phys_mapping_valid' follow
> 

      reply	other threads:[~2011-06-10 12:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  9:53 [PATCH 00 of 12] xenpaging fixes for xen-unstable Olaf Hering
2011-06-07  9:53 ` [PATCH 01 of 12] xenpaging: correct dropping of pages to avoid full ring buffer Olaf Hering
2011-06-07  9:53 ` [PATCH 02 of 12] xenpaging: do not bounce p2mt to xenpaging Olaf Hering
2011-06-07  9:53 ` [PATCH 03 of 12] xenpaging: remove srand call Olaf Hering
2011-06-07  9:53 ` [PATCH 04 of 12] xenpaging: remove return values from functions that can not fail Olaf Hering
2011-06-07  9:53 ` [PATCH 05 of 12] xenpaging: catch xc_mem_paging_resume errors Olaf Hering
2011-06-07  9:53 ` [PATCH 06 of 12] xenpaging: remove local domain_id variable Olaf Hering
2011-06-07  9:53 ` [PATCH 07 of 12] xenpaging: move num_pages into xenpaging struct Olaf Hering
2011-06-07  9:53 ` [PATCH 08 of 12] xenpaging: start paging in the middle of gfn range Olaf Hering
2011-06-07  9:53 ` [PATCH 09 of 12] xenpaging: pass integer to xenpaging_populate_page Olaf Hering
2011-06-07  9:53 ` [PATCH 10 of 12] xenpaging: add helper function for unlinking pagefile Olaf Hering
2011-06-07  9:53 ` [PATCH 11 of 12] xenpaging: add watch thread to catch guest shutdown Olaf Hering
2011-06-07 10:23   ` Ian Campbell
2011-06-07 19:07     ` Olaf Hering
2011-06-07  9:53 ` [PATCH 12 of 12] xenpaging: implement stopping of pager by sending SIGTERM/SIGINT Olaf Hering
2011-06-07 12:27 ` [PATCH 00 of 12] xenpaging fixes for xen-unstable Keir Fraser
2011-06-07 13:38   ` Olaf Hering
2011-06-08 16:01     ` Keir Fraser
2011-06-10  7:28     ` Keir Fraser
2011-06-10 11:27       ` Olaf Hering
2011-06-10 12:52         ` Keir Fraser [this message]

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=CA17D216.1C07E%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=olaf@aepfle.de \
    --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).