All of lore.kernel.org
 help / color / mirror / Atom feed
From: "wilbur.chan" <wilbur512@gmail.com>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: linux-mips@linux-mips.org, kexec@lists.infradead.org,
	horms@verge.net.au, ralf@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS kexec,kdump support
Date: Thu, 4 Mar 2010 00:34:22 +0800	[thread overview]
Message-ID: <e997b7421003030834r7bec3295s7917bb91a3fa2d27@mail.gmail.com> (raw)
In-Reply-To: <20100303110527.11233.20400.stgit@muvarov>

2010/3/3 Maxim Uvarov <muvarov@gmail.com>:
> Hello folks,
>
> Please find here MIPS crash and kdump patches.
> This is patch set of 3 patches:
> 1. generic MIPS changes (kernel);
> 2. MIPS Cavium Octeon board kexec/kdump code (kernel);
> 3. Kexec user space MIPS changes.
>
> Patches were tested on the latest linux-mips@ git kernel and the latest
> kexec-tools git on Cavium Octeon 50xx board.
>
> I also made the same code working on RMI XLR/XLS boards for both
> mips32 and mips64 kernels.
>
> Best regards,
> Maxim Uvarov.
>

> Signed-off-by: Maxim Uvarov <muvarov@gmail.com>
>
>
>

Hi, Maxim

In XLR series ,

1)How to protect  boardinfo and pass it to second kernel ?

2)If all cpus jumped to same entry point , did you change head.s  ,if so , how ?



Thank you!

WARNING: multiple messages have this Message-ID (diff)
From: "wilbur.chan" <wilbur512@gmail.com>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: linux-mips@linux-mips.org, horms@verge.net.au,
	kexec@lists.infradead.org, ralf@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS kexec,kdump support
Date: Thu, 4 Mar 2010 00:34:22 +0800	[thread overview]
Message-ID: <e997b7421003030834r7bec3295s7917bb91a3fa2d27@mail.gmail.com> (raw)
In-Reply-To: <20100303110527.11233.20400.stgit@muvarov>

2010/3/3 Maxim Uvarov <muvarov@gmail.com>:
> Hello folks,
>
> Please find here MIPS crash and kdump patches.
> This is patch set of 3 patches:
> 1. generic MIPS changes (kernel);
> 2. MIPS Cavium Octeon board kexec/kdump code (kernel);
> 3. Kexec user space MIPS changes.
>
> Patches were tested on the latest linux-mips@ git kernel and the latest
> kexec-tools git on Cavium Octeon 50xx board.
>
> I also made the same code working on RMI XLR/XLS boards for both
> mips32 and mips64 kernels.
>
> Best regards,
> Maxim Uvarov.
>

> Signed-off-by: Maxim Uvarov <muvarov@gmail.com>
>
>
>

Hi, Maxim

In XLR series ,

1)How to protect  boardinfo and pass it to second kernel ?

2)If all cpus jumped to same entry point , did you change head.s  ,if so , how ?



Thank you!

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2010-03-03 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 11:05 [PATCH 1/2] MIPS kexec,kdump support Maxim Uvarov
2010-03-03 11:05 ` Maxim Uvarov
2010-03-03 11:05 ` [PATCH 2/2] MIPS Cavium Octeon board " Maxim Uvarov
2010-03-03 11:05   ` Maxim Uvarov
2010-03-03 16:34 ` wilbur.chan [this message]
2010-03-03 16:34   ` [PATCH 1/2] MIPS " wilbur.chan
2010-03-04 11:58   ` Maxim Uvarov
2010-03-04 11:58     ` Maxim Uvarov
2010-03-03 17:36 ` David Daney
2010-03-04 11:35   ` Maxim Uvarov
2010-03-04 11:35     ` Maxim Uvarov

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=e997b7421003030834r7bec3295s7917bb91a3fa2d27@mail.gmail.com \
    --to=wilbur512@gmail.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-mips@linux-mips.org \
    --cc=muvarov@gmail.com \
    --cc=ralf@linux-mips.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 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.