All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Wray <mike.wray@hp.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	Xen Mailing List <xen-devel@lists.xensource.com>,
	Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: dom0 bootstrap for xenstore
Date: Fri, 17 Jun 2005 14:00:49 +0100	[thread overview]
Message-ID: <42B2C981.5020104@hp.com> (raw)
In-Reply-To: <1118993482.12389.43.camel@localhost.localdomain>

Rusty Russell wrote:
> On Thu, 2005-06-16 at 14:55 +0100, Keir Fraser wrote:
> 
>>On 16 Jun 2005, at 09:11, Rusty Russell wrote:
>>
>>
>>>So here's my patch against latest bk, including test program but we 
>>>have
>>>an issue.  On unmap, I hit the BUG_ON() on mm/rmap.c:482.  Is this some
>>>issue with using xc_map_foreign_range() on non-foreign pages?
>>
>>Ah, it's not working because xc_map_foreign_range does not raise 
>>refcnts on the page being mapped.
> 
> 
> OK, fixed, please apply the below patch against current bk.
> 
> Mike, this means backing out your changes to use domain_info to
> communicate this.  I didn't try to extricate that...
> 

OK, I fixed up the domain introduce code to use the privcmd for
dom0 and applied the change to make the page reserved.
The good news is that introducing dom0 to xenstore now works, and
mapping the store page works too.
The bad news is that the dom0 xenbus probe oopses as follows:

bounds: 0000 [#1]
PREEMPT
Modules linked in:
CPU:    0
EIP:    0061:[<c055d940>]    Not tainted VLI
EFLAGS: 00010246   (2.6.11.11-xen0)
EIP is at xenbus_probe_init+0x0/0x80
eax: 00000000   ebx: c5544000   ecx: 00000002   edx: 00000000
esi: c5a0fd10   edi: 00000000   ebp: c02c0ac0   esp: c5545fc4
ds: 007b   es: 007b   ss: 0069
Process xenbus_probe (pid: 2310, threadinfo=c5544000 task=c5521a00)
Stack: c01332ca 00000000 c5545fd8 00000000 fffffffc ffffffff ffffffff c0133220
        00000000 00000000 00000000 c0107b75 c5a0fd10 00000000 00000000
Call Trace:
  [<c01332ca>] kthread+0xaa/0xb0
  [<c0133220>] kthread+0x0/0xb0
  [<c0107b75>] kernel_thread_helper+0x5/0x10
Code: 75 67 69 6e 2e 73 6f 00 6c 69 62 6b 6f 6e 71 5f 73 69 64 65 62 61 72 5f 74 72 65 65 2
e 73 6f 00 2f 75 73 72 2f 6c 69 62 2f 6c 69 <62> 6b 6f 6e 71 5f 73 69 64 65 62 61 72 5f 74
72 65 65 2e 73 6f

Regards,

Mike

  reply	other threads:[~2005-06-17 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A95E2296287EAD4EB592B5DEEFCE0E9D282251@liverpoolst.ad.cl.cam.ac.uk>
     [not found] ` <1118891075.15491.14.camel@localhost.localdomain>
     [not found]   ` <ea6e31bae1f900c7b076535f372290a3@cl.cam.ac.uk>
2005-06-16  8:11     ` dom0 bootstrap for xenstore Rusty Russell
2005-06-16 13:55       ` Keir Fraser
2005-06-16 14:03         ` Keir Fraser
2005-06-16 15:54         ` Mike Wray
2005-06-16 19:40           ` Keir Fraser
2005-06-17  3:50         ` Rusty Russell
2005-06-17  7:31         ` Rusty Russell
2005-06-17 13:00           ` Mike Wray [this message]
2005-06-20  4:49             ` Rusty Russell
2005-06-20 15:39               ` Mike Wray

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=42B2C981.5020104@hp.com \
    --to=mike.wray@hp.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=rusty@rustcorp.com.au \
    --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 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.