On Tue, Jul 16, 2013 at 05:37:09PM +0200, Michael Holzheu wrote:
[..]
> The problem is that with the mmap patches we now use copy_oldmem_page()
> to copy the notes from oldmem into the notes_buf which has been allocated
> with vmalloc. The s390 version of copy_oldmem_page() bypasses the page
>
On Tue, 16 Jul 2013 10:04:18 -0400
Vivek Goyal wrote:
> On Tue, Jul 16, 2013 at 11:25:27AM +0200, Michael Holzheu wrote:
>
> [..]
> > > > Hello Vivek and Andrew,
> > > >
> > > > We just realized that Hatayama's mmap patches went into v3.11-rc1. This
> > > > currently
> > > > breaks s390 kdump
On Tue, Jul 16, 2013 at 11:25:27AM +0200, Michael Holzheu wrote:
[..]
> > > Hello Vivek and Andrew,
> > >
> > > We just realized that Hatayama's mmap patches went into v3.11-rc1. This
> > > currently
> > > breaks s390 kdump because of the following two issues:
> > >
> > > 1) The
(2013/07/16 9:27), HATAYAMA Daisuke wrote:
(2013/07/15 23:20), Vivek Goyal wrote:
On Fri, Jul 12, 2013 at 08:05:31PM +0900, HATAYAMA Daisuke wrote:
[..]
How about
static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
{
...
char *buf;
int rc;
On Mon, 15 Jul 2013 10:27:08 -0400
Vivek Goyal wrote:
> On Mon, Jul 15, 2013 at 03:44:51PM +0200, Michael Holzheu wrote:
> > On Tue, 2 Jul 2013 11:42:14 -0400
> > Vivek Goyal wrote:
> >
> > > On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
> > > > For zfcpdump we can't map the
On Mon, 15 Jul 2013 10:27:08 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Mon, Jul 15, 2013 at 03:44:51PM +0200, Michael Holzheu wrote:
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
For
(2013/07/16 9:27), HATAYAMA Daisuke wrote:
(2013/07/15 23:20), Vivek Goyal wrote:
On Fri, Jul 12, 2013 at 08:05:31PM +0900, HATAYAMA Daisuke wrote:
[..]
How about
static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
{
...
char *buf;
int rc;
On Tue, Jul 16, 2013 at 11:25:27AM +0200, Michael Holzheu wrote:
[..]
Hello Vivek and Andrew,
We just realized that Hatayama's mmap patches went into v3.11-rc1. This
currently
breaks s390 kdump because of the following two issues:
1) The copy_oldmem_page() is now used for
On Tue, 16 Jul 2013 10:04:18 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Tue, Jul 16, 2013 at 11:25:27AM +0200, Michael Holzheu wrote:
[..]
Hello Vivek and Andrew,
We just realized that Hatayama's mmap patches went into v3.11-rc1. This
currently
breaks s390 kdump
On Tue, Jul 16, 2013 at 05:37:09PM +0200, Michael Holzheu wrote:
[..]
The problem is that with the mmap patches we now use copy_oldmem_page()
to copy the notes from oldmem into the notes_buf which has been allocated
with vmalloc. The s390 version of copy_oldmem_page() bypasses the page
tables
(2013/07/15 18:21), Martin Schwidefsky wrote:
On Sat, 13 Jul 2013 01:02:50 +0900
HATAYAMA Daisuke wrote:
(2013/07/10 20:00), Michael Holzheu wrote:
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke wrote:
[snip]
(2013/07/10 17:42), Michael Holzheu wrote:
My suggestion is to add the
(2013/07/15 23:20), Vivek Goyal wrote:
On Fri, Jul 12, 2013 at 08:05:31PM +0900, HATAYAMA Daisuke wrote:
[..]
How about
static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
{
...
char *buf;
int rc;
#ifndef CONFIG_S390
return
On Mon, Jul 15, 2013 at 03:44:51PM +0200, Michael Holzheu wrote:
> On Tue, 2 Jul 2013 11:42:14 -0400
> Vivek Goyal wrote:
>
> > On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
> > > For zfcpdump we can't map the HSA storage because it is only available
> > > via a read
On Fri, Jul 12, 2013 at 08:05:31PM +0900, HATAYAMA Daisuke wrote:
[..]
> How about
>
> static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
> {
> ...
> char *buf;
> int rc;
>
> #ifndef CONFIG_S390
> return VM_FAULT_SIGBUS;
> #endif
>
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal wrote:
> On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
> > For zfcpdump we can't map the HSA storage because it is only available
> > via a read interface. Therefore, for the new vmcore mmap feature we have
> > introduce a new
On Sat, 13 Jul 2013 01:02:50 +0900
HATAYAMA Daisuke wrote:
> (2013/07/10 20:00), Michael Holzheu wrote:
> > On Wed, 10 Jul 2013 18:50:18 +0900
> > HATAYAMA Daisuke wrote:
> >
> > [snip]
> >
> >> (2013/07/10 17:42), Michael Holzheu wrote:
> >>> My suggestion is to add the WARN_ONCE() for #ifndef
On Sat, 13 Jul 2013 01:02:50 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/10 20:00), Michael Holzheu wrote:
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
[snip]
(2013/07/10 17:42), Michael Holzheu wrote:
My suggestion is to
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce
On Fri, Jul 12, 2013 at 08:05:31PM +0900, HATAYAMA Daisuke wrote:
[..]
How about
static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
{
...
char *buf;
int rc;
#ifndef CONFIG_S390
return VM_FAULT_SIGBUS;
#endif
page =
On Mon, Jul 15, 2013 at 03:44:51PM +0200, Michael Holzheu wrote:
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read
(2013/07/15 23:20), Vivek Goyal wrote:
On Fri, Jul 12, 2013 at 08:05:31PM +0900, HATAYAMA Daisuke wrote:
[..]
How about
static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
{
...
char *buf;
int rc;
#ifndef CONFIG_S390
return
(2013/07/15 18:21), Martin Schwidefsky wrote:
On Sat, 13 Jul 2013 01:02:50 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/10 20:00), Michael Holzheu wrote:
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
[snip]
(2013/07/10 17:42),
(2013/07/10 20:00), Michael Holzheu wrote:
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke wrote:
[snip]
(2013/07/10 17:42), Michael Holzheu wrote:
My suggestion is to add the WARN_ONCE() for #ifndef CONFIG_S390. This has the
same
effect as your suggestion for all architectures besides
(2013/07/10 23:33), Vivek Goyal wrote:
On Wed, Jul 10, 2013 at 06:50:18PM +0900, HATAYAMA Daisuke wrote:
[..]
If you want to avoid looking up vmcore_list that takes linear time w.r.t. the
number
of the elements, you can still calculate the range of offsets in /proc/vmcore
corresponding to HSA
(2013/07/10 23:33), Vivek Goyal wrote:
On Wed, Jul 10, 2013 at 06:50:18PM +0900, HATAYAMA Daisuke wrote:
[..]
If you want to avoid looking up vmcore_list that takes linear time w.r.t. the
number
of the elements, you can still calculate the range of offsets in /proc/vmcore
corresponding to HSA
(2013/07/10 20:00), Michael Holzheu wrote:
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
[snip]
(2013/07/10 17:42), Michael Holzheu wrote:
My suggestion is to add the WARN_ONCE() for #ifndef CONFIG_S390. This has the
same
effect as your suggestion for
On Wed, Jul 10, 2013 at 06:50:18PM +0900, HATAYAMA Daisuke wrote:
[..]
> If you want to avoid looking up vmcore_list that takes linear time w.r.t. the
> number
> of the elements, you can still calculate the range of offsets in /proc/vmcore
> corresponding to HSA during /proc/vmcore
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke wrote:
[snip]
> (2013/07/10 17:42), Michael Holzheu wrote:
> > My suggestion is to add the WARN_ONCE() for #ifndef CONFIG_S390. This has
> > the same
> > effect as your suggestion for all architectures besides of s390. And for
> > s390 we
>
(2013/07/10 17:42), Michael Holzheu wrote:
Hello Hatayama,
On Tue, 09 Jul 2013 14:49:48 +0900
HATAYAMA Daisuke wrote:
(2013/07/08 23:28), Vivek Goyal wrote:
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke wrote:
[snip]
Hello Hatayama,
On Tue, 09 Jul 2013 14:49:48 +0900
HATAYAMA Daisuke wrote:
> (2013/07/08 23:28), Vivek Goyal wrote:
> > On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
> >> On Mon, 08 Jul 2013 14:32:09 +0900
> >> HATAYAMA Daisuke wrote:
[snip]
> > I personally perfer not to
Hello Hatayama,
On Tue, 09 Jul 2013 14:49:48 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/08 23:28), Vivek Goyal wrote:
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/10 17:42), Michael Holzheu wrote:
Hello Hatayama,
On Tue, 09 Jul 2013 14:49:48 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/08 23:28), Vivek Goyal wrote:
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
[snip]
(2013/07/10 17:42), Michael Holzheu wrote:
My suggestion is to add the WARN_ONCE() for #ifndef CONFIG_S390. This has
the same
effect as your suggestion for all architectures besides of s390. And
On Wed, Jul 10, 2013 at 06:50:18PM +0900, HATAYAMA Daisuke wrote:
[..]
If you want to avoid looking up vmcore_list that takes linear time w.r.t. the
number
of the elements, you can still calculate the range of offsets in /proc/vmcore
corresponding to HSA during /proc/vmcore initialization.
(2013/07/08 23:28), Vivek Goyal wrote:
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke wrote:
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read
(2013/07/08 18:28), Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke wrote:
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
> On Mon, 08 Jul 2013 14:32:09 +0900
> HATAYAMA Daisuke wrote:
>
> > (2013/07/02 4:32), Michael Holzheu wrote:
> > > For zfcpdump we can't map the HSA storage because it is only available
> > > via a read interface. Therefore, for
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke wrote:
> (2013/07/02 4:32), Michael Holzheu wrote:
> > For zfcpdump we can't map the HSA storage because it is only available
> > via a read interface. Therefore, for the new vmcore mmap feature we have
> > introduce a new mechanism to create
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce a new
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface.
(2013/07/08 18:28), Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore
(2013/07/08 23:28), Vivek Goyal wrote:
On Mon, Jul 08, 2013 at 11:28:39AM +0200, Michael Holzheu wrote:
On Mon, 08 Jul 2013 14:32:09 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce a new mechanism to create mappings on demand.
This patch introduces a new architecture function
(2013/07/02 4:32), Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce a new mechanism to create mappings on demand.
This patch introduces a new architecture function
On Wed, Jul 03, 2013 at 03:59:33PM +0200, Michael Holzheu wrote:
> On Tue, 2 Jul 2013 11:42:14 -0400
> Vivek Goyal wrote:
>
> > On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
>
> [snip]
>
> > > This handler works as follows:
> > >
> > > * Get already available or new page
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal wrote:
> On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
[snip]
> > This handler works as follows:
> >
> > * Get already available or new page from page cache (find_or_create_page)
> > * Check if /proc/vmcore page is filled with
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
[snip]
This handler works as follows:
* Get already available or new page from page cache (find_or_create_page)
* Check if /proc/vmcore page is
On Wed, Jul 03, 2013 at 03:59:33PM +0200, Michael Holzheu wrote:
On Tue, 2 Jul 2013 11:42:14 -0400
Vivek Goyal vgo...@redhat.com wrote:
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
[snip]
This handler works as follows:
* Get already available or new page
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
> For zfcpdump we can't map the HSA storage because it is only available
> via a read interface. Therefore, for the new vmcore mmap feature we have
> introduce a new mechanism to create mappings on demand.
>
> This patch introduces
On Mon, Jul 01, 2013 at 09:32:37PM +0200, Michael Holzheu wrote:
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce a new mechanism to create mappings on demand.
This patch introduces a new
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce a new mechanism to create mappings on demand.
This patch introduces a new architecture function remap_oldmem_pfn_range()
that should be used to
For zfcpdump we can't map the HSA storage because it is only available
via a read interface. Therefore, for the new vmcore mmap feature we have
introduce a new mechanism to create mappings on demand.
This patch introduces a new architecture function remap_oldmem_pfn_range()
that should be used to
52 matches
Mail list logo
