mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ed Swierk <eswierk@arastra.com>
To: linux-kernel@vger.kernel.org
Subject: Longer command line for kexec on i386
Date: Mon, 23 Jul 2007 15:42:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070723T172709-232@post.gmane.org> (raw)

I'm attempting to get kexec to pass a command line longer than 256 bytes to the
new kernel, using kexec-tools-testing-20070330 and kernel 2.6.22.1.  The new
kernel is a bzImage, and I'm using kexec to tack on a command line and an initrd.

I made the following change to kexec:

--- kexec-tools-testing-20070330.orig/include/x86/x86-linux.h
+++ kexec-tools-testing-20070330/include/x86/x86-linux.h
@@ -148,14 +148,13 @@
 #endif
        struct e820entry e820_map[E820MAX];     /* 0x2d0 */
                                                /* 0x550 */
-#define COMMAND_LINE_SIZE 256
+#define COMMAND_LINE_SIZE 2048
 };

 struct x86_linux_faked_param_header {
        struct x86_linux_param_header hdr;      /* 0x00 */
        uint8_t reserved16[688];                /* 0x550 */
-       uint8_t command_line[COMMAND_LINE_SIZE]; /* 0x800 */
-       uint8_t reserved17[1792];               /* 0x900 - 0x1000 */
+       uint8_t command_line[COMMAND_LINE_SIZE]; /* 0x800 - 0x1000 */
 };

 struct x86_linux_header {

but I'm now seeing intermittent corruption of the initrd in the new kernel--a
few bytes at different locations each time.

I suspect I've neglected some other important changes to the boot protocol.  Any
clues would be appreciated.

Thanks,
--Ed



             reply	other threads:[~2007-07-23 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 15:42 Ed Swierk [this message]
2007-07-25 16:50 ` Ed Swierk

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=loom.20070723T172709-232@post.gmane.org \
    --to=eswierk@arastra.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®