All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Wray <mike.wray@hpl.hp.com>
To: Matthew Bloch <matthew@bytemark.co.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: PATCH: ability to send sysrqs to Linux domains
Date: Thu, 09 Dec 2004 17:43:59 +0000	[thread overview]
Message-ID: <41B88EDF.9030906@hpl.hp.com> (raw)
In-Reply-To: <cp9drl$qoj$1@sea.gmane.org>

Matthew Bloch wrote:
> Here's the promised patch against a recent 2.01 snapshot to allow you to 
> send sysrqs to running Linux kernels.  I went with Keir's suggestion of 
> adding a sub-reason code to the shutdown message with a 1-byte payload 
> specifying which key was pressed.  Hope it's acceptable for the main 
> tree; I will happily alter it to spec if any of the maintainers have 
> suggestions for better structuring it.

There's a slight problem with the client/server python code.
On the client side you have

def xend_domain_shutdown(self, id, reason, key=None):
         return self.xendPost(self.domainurl(id),
                              {'op'      : 'shutdown',
                               'reason'  : reason,
                               'key'     : key })

while on the server side you have

  fn = FormFn(self.xd.domain_shutdown,
              [['dom', 'str'],
               ['reason', 'str'],
               ['key', 'int']])

which means 'key' has to be an int.
So passing 'None' is going to cause an error.

Mike


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

      reply	other threads:[~2004-12-09 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 11:44 PATCH: ability to send sysrqs to Linux domains Matthew Bloch
2004-12-09 17:43 ` Mike Wray [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=41B88EDF.9030906@hpl.hp.com \
    --to=mike.wray@hpl.hp.com \
    --cc=matthew@bytemark.co.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.