All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dulloor <dulloor@gmail.com>
Cc: Boris Derzhavets <bderzhavets@yahoo.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	"Marc - A. Dahlhaus" <mad@wol.de>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: pvops DomU kernels [was Re: "Hotplug Scripts not working ..." error on jaunty]
Date: Fri, 23 Oct 2009 13:37:08 -0700	[thread overview]
Message-ID: <4AE213F4.7020204@goop.org> (raw)
In-Reply-To: <940bcfd20910230121r174c7876m230c0b2728495b56@mail.gmail.com>

On 10/23/09 01:21, Dulloor wrote:
> * jeremy pvops git (with SMP) - Your patch works. I had commented out
> detect_extended_topology as a work-around.
>   

OK, good.

> * jeremy pvops git (without SMP) - Build fails at link time, since
> "register_task_migration_notifier" definition is guarded by CONFIG_SMP
> (rightly so). This function is used in pvclock_init_vsyscall. Should
> the call in pvclock_init_vsyscall be guarded by CONFIG_SMP or should
> another "dummy" version of register_task_migration_notifier be defined
> for !CONFIG_SMP.
>   

Yes, the second sounds like the right answer.

> * Linus' git - Nothing on Linux console. Crash rip [BUG()] -
> (gdb) x/i 0xffffffff818da4ee
> 0xffffffff818da4ee <xen_load_gdt_boot+272>:     ud2a
>
> Crash is because HYPERVISOR_update_va_mapping fails.
>
> I have attached the "xm dmesg", which also shows the error(in mm.c)
> leading to the crash. If you can't think of any existing problem, I
> will spend time debugging tomorrow.
>   

Its not at all clear to me what Xen is objecting to here.  There are a
few paths where it can end up at could_not_pin in get_page_from_l1e(),
but I don't know which one is happening here.  I think it's the "if (
unlikely(real_pg_owner != pg_owner) )" conditional, but I don't know
what real_pg_owner means here.

Keir?

    J

  reply	other threads:[~2009-10-23 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22  5:56 pvops DomU kernels [was Re: "Hotplug Scripts not working ..." error on jaunty] Dulloor
2009-10-22  7:44 ` Boris Derzhavets
2009-10-22 21:04 ` Jeremy Fitzhardinge
2009-10-23  8:21   ` Dulloor
2009-10-23 20:37     ` Jeremy Fitzhardinge [this message]
2009-10-23 20:48       ` Keir Fraser
2009-10-23 20:58         ` Jeremy Fitzhardinge
2009-10-24  7:43           ` Keir Fraser

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=4AE213F4.7020204@goop.org \
    --to=jeremy@goop.org \
    --cc=bderzhavets@yahoo.com \
    --cc=dulloor@gmail.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=mad@wol.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 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.