, thanks for coding this up.
Bob Montgomery
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
that all looks good.
Then the next LOAD is also at 2400 with a 0 in the size fields.
I haven't had a chance to check the code yet.
Bob Montgomery
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
On Tue, 2008-09-23 at 02:29 +, Eric W. Biederman wrote:
Bob Montgomery [EMAIL PROTECTED] writes:
And that leads to the Kdump IO Rule:
The primary kernel is responsible for setting up any necessary
conditions to allow the kdump kernel to perform its required
by the kdump kernel, remapped by the Intel
IOMMU to those same addresses (iova equals physical address
within the Crash kernel area).
This all assumes no virtual machine stuff yet.
Possible? Comments? Corrections?
Bob Montgomery
___
kexec
On Fri, 2008-09-05 at 15:12 +, Vivek Goyal wrote:
Nice summary Bob. Few thoughts.
- So until and unless one is reserving memory for crashkernel above 4G,
there is no need for initializing the IOMMU in second kernel (At this
moment I am not too worried about need of isolation in second
to copy the result into the real buffer.
What considerations have I missed?
Bob Montgomery
(vacation last week)
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
On Tue, 2008-07-08 at 13:28 +, Vivek Goyal wrote:
On Mon, Jul 07, 2008 at 05:08:06PM -0600, Bob Montgomery wrote:
We maintain a 2.6.18 derived kernel.
When testing kdump on a new AMD Family 10h (16) processor, once in the
kdump kernel, a read from either /proc/vmcore or /dev/oldmem
it be excluded from the /proc/vmcore list of areas??
Thanks for any insights,
Bob Montgomery
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
