All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>,
	Jun Koi <junkoi2004@gmail.com>
Subject: Re: gdbsx?
Date: Wed, 03 Sep 2008 15:57:10 -0700	[thread overview]
Message-ID: <48BF1646.2020501@oracle.com> (raw)
In-Reply-To: <C4E1D5D8.26A4B%keir.fraser@eu.citrix.com>


 >Mukesh: Could you explain a bit the advantage of gdbsx over the
 >current implementation that is already in tree? I figured out some,
 >but still might miss some. That is not very clear from the slides.

I've not used the current implementation in the tree so can't compare.
The main reason for gdbsx is because we use 32bit dom0 on 64bit hypervisor,
and I couldn't get libxc to support that after a lot of effort.

What I can tell you about gdbsx is, it's a clean, simplified, lightweight
implementation, that relies on the hyp for most of the work with minimal
changes. It supports all guests, PV or HVM, 32bit or 64bit.


Keir Fraser wrote:
 > On 1/9/08 17:15, "Jun Koi" <junkoi2004@gmail.com> wrote:
 >
 > It has some chance, if it is used and if it is cleanly implemented. Equally
 > for now it ought to be able to live quite happily outside of the main
 > repository.
 >
 >  -- Keir

gdbsx currently works on 32bit dom0 running on 64bit hyp, hence, probably
not ready for the main repo. OTOH, kdb is getting there....

thanks,
mukesh

  reply	other threads:[~2008-09-03 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 15:59 gdbsx? Jun Koi
2008-09-01 16:06 ` gdbsx? Keir Fraser
2008-09-01 16:15   ` gdbsx? Jun Koi
2008-09-01 16:24     ` gdbsx? Keir Fraser
2008-09-03 22:57       ` Mukesh Rathor [this message]
2008-09-05  3:44         ` gdbsx? Jun Koi
2008-09-03  0:45   ` gdbsx? Mukesh Rathor

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=48BF1646.2020501@oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=junkoi2004@gmail.com \
    --cc=keir.fraser@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 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.