From: Chandru <chandru@in.ibm.com>
To: bob.montgomery@hp.com
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: kdump: quad core Opteron
Date: Wed, 08 Oct 2008 19:21:49 +0530 [thread overview]
Message-ID: <48ECBAF5.5010309@in.ibm.com> (raw)
In-Reply-To: <1223395191.2215.179.camel@amd.troyhebe>
Bob Montgomery wrote:
> Here's the README for the patch:
>
> This patch changes the initialization of the GART (in
> pci-gart.c:init_k8_gatt) to set the DisGartCpu bit in the GART Aperture
> Control Register. Setting the bit Disables requests from the CPUs from
> accessing the GART. In other words, CPU memory accesses within the
> range of addresses in the aperture will not cause the GART to perform an
> address translation. The aperture area was already being unmapped at
> the kernel level with clear_kernel_mapping() to prevent accesses from
> the CPU, but that kernel level unmapping is not in effect in the kexec'd
> kdump kernel. By disabling the CPU-side accesses within the GART, which
> does persist through the kexec of the kdump kernel, the kdump kernel is
> prevented from interacting with the GART during accesses to the dump
> memory areas which include the address range of the GART aperture.
> Although the patch can be applied to the kdump kernel, it is not
> exercised there because the kdump kernel doesn't attempt to initialize
> the GART.
>
> Bob Montgomery
> working at HP
>
>
I made the following changes and it seems like it is working.
--- linux-2.6.27-rc8/include/asm-x86/gart.h.orig 2008-10-08
09:41:23.000000000 -0400
+++ linux-2.6.27-rc8/include/asm-x86/gart.h 2008-10-08
09:44:35.000000000 -0400
@@ -42,7 +42,8 @@ static inline void enable_gart_translati
/* Enable GART translation for this hammer. */
pci_read_config_dword(dev, AMD64_GARTAPERTURECTL, &ctl);
ctl |= GARTEN;
- ctl &= ~(DISGARTCPU | DISGARTIO);
+ ctl |= DISGARTCPU;
+ ctl &= ~(DISGARTIO);
pci_write_config_dword(dev, AMD64_GARTAPERTURECTL, ctl);
}
The system doesn't reset now while copying /proc/vmcore. Thanks!
Chandru
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-10-08 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 12:51 kdump: quad core Opteron Chandru
2008-10-07 13:06 ` Bernhard Walle
2008-10-07 13:24 ` Vivek Goyal
2008-10-07 15:59 ` Bob Montgomery
2008-10-08 13:51 ` Chandru [this message]
2008-12-08 15:56 ` Chandru
2008-12-08 21:54 ` Vivek Goyal
2008-12-09 12:12 ` Chandru
2008-12-09 18:55 ` Bob Montgomery
2008-12-08 23:35 ` Bob Montgomery
2008-12-09 1:32 ` Neil Horman
2008-12-09 11:59 ` Chandru
2008-10-08 13:40 ` Chandru
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=48ECBAF5.5010309@in.ibm.com \
--to=chandru@in.ibm.com \
--cc=bob.montgomery@hp.com \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox