All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <christian.limpach@gmail.com>
To: Kip Macy <kmacy@netapp.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] make domu_debug run-time option + fix int3 handling for MP
Date: Mon, 16 May 2005 22:55:49 +0100	[thread overview]
Message-ID: <3d8eece20505161455119d8dc2@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0505151819570.16537-100000@octopus.eng.netapp.com>

On 5/16/05, Kip Macy <kmacy@netapp.com> wrote:
> I'm not entirely thrilled with the interfaces used to get the domu_debug option
> into xen, but adding yet another argument xc_linux_build and/or adding a
> separate handler for domu_debug didn't seem that clean either. The debug support
> doesn't seem like something Ron would use, so I didn't update the Plan 9
> builder.

Looks allright -- except that the debugger.h changes break the
non-domu_debug usages.  Even if you fix that, I'm not sure we want
debugger_trap_entry to be domu_debug only.  Could you please explain
what the intent is and resend as separate patches?
Maybe a debug_trap_entry wrapper which tests the DOMF_debug flag and
either calls the domu_debug function or the other debugger function
would be better?  Please also leave the #if/#elif construct for easy
switching between the different debugger stubs...

     christian

  parent reply	other threads:[~2005-05-16 21:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  1:25 [PATCH] make domu_debug run-time option + fix int3 handling for MP Kip Macy
2005-05-16 19:07 ` possible changes was " Kip Macy
2005-05-16 20:10   ` Keir Fraser
2005-05-16 20:26     ` Kip Macy
2005-05-16 20:28       ` Keir Fraser
2005-05-16 20:33         ` Kip Macy
2005-05-16 20:40           ` Keir Fraser
2005-05-16 20:46             ` Kip Macy
2005-05-16 21:55 ` Christian Limpach [this message]
2005-05-16 22:08   ` Kip Macy
2005-05-16 22:18     ` Christian Limpach
2005-05-16 22:23       ` Kip Macy

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=3d8eece20505161455119d8dc2@mail.gmail.com \
    --to=christian.limpach@gmail.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=kmacy@netapp.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.