From: Oleg Nesterov <oleg@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alex Thorlton <athorlton@sgi.com>,
Peter Zijlstra <peterz@infradead.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, schwidefsky@de.ibm.com,
rientjes@google.com, riel@redhat.com, mingo@kernel.org,
mgorman@suse.de,
kirill shutemov <kirill.shutemov@linux.intel.com>,
heiko carstens <heiko.carstens@de.ibm.com>,
hannes@cmpxchg.org, gerald schaefer <gerald.schaefer@de.ibm.com>,
ebiederm@xmission.com, aarcange@redhat.com
Subject: Re: + mm-revert-thp-make-madv_hugepage-check-for-mm-def_flags.patch added to -mm tree
Date: Thu, 27 Feb 2014 17:34:05 +0100 [thread overview]
Message-ID: <20140227163405.GA909@redhat.com> (raw)
In-Reply-To: <842178473.10219645.1393447292444.JavaMail.zimbra@redhat.com>
On 02/26, Paolo Bonzini wrote:
>
> > +#ifdef CONFIG_S390
> > + /*
> > + * MADV_HUGEPAGE is broken after s390_enable_sie(), qemu
> > + * blindly does madvise(MADV_HUGEPAGE) for for all kvm pages
> > + * and expects it must fail on s390. Avoid a possible SIGSEGV
> > + * until qemu is changed.
> > + */
> > + if (mm_has_pgste(vma->vm_mm))
> > + return -EINVAL;
> > +#endif
>
> The comment is not quite true. QEMU doesn't expect that the madvise fails.
Yes, sorry. I didn't mean "it expects -EINVAL".
> It simply expects that the madvise doesn't cause SIGSEGVs or later
> malfunctioning, because (quoting tha man page) madvise "does not influence
> the semantics of the application".
Yes, I understand. But currently this means "MADV_HUGEPAGE should not
actually work", this is what I tried to say.
> There's nothing to fix in QEMU,
I was going to argue, but this is probably true too.
In short: I agree with any comment ;)
Oleg.
next prev parent reply other threads:[~2014-02-27 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <530d2ce9.eikv0ULecNwxF4I5%akpm@linux-foundation.org>
[not found] ` <530D9F50.1080400@de.ibm.com>
2014-02-26 14:50 ` + mm-revert-thp-make-madv_hugepage-check-for-mm-def_flags.patch added to -mm tree Oleg Nesterov
2014-02-26 15:06 ` Christian Borntraeger
2014-02-26 15:22 ` Kirill A. Shutemov
2014-02-26 15:31 ` Oleg Nesterov
2014-02-26 16:55 ` Gerald Schaefer
2014-02-26 16:57 ` Peter Zijlstra
2014-02-26 17:22 ` Alex Thorlton
2014-02-26 18:06 ` Oleg Nesterov
2014-02-26 19:05 ` Gerald Schaefer
2014-02-27 16:45 ` Oleg Nesterov
2014-02-26 19:27 ` Christian Borntraeger
2014-02-26 19:39 ` Alex Thorlton
2014-02-26 23:24 ` Andrew Morton
2014-02-27 0:01 ` Alex Thorlton
2014-02-27 17:26 ` Alex Thorlton
2014-02-26 20:41 ` Paolo Bonzini
2014-02-27 16:34 ` Oleg Nesterov [this message]
2014-02-26 18:08 ` Oleg Nesterov
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=20140227163405.GA909@redhat.com \
--to=oleg@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=borntraeger@de.ibm.com \
--cc=ebiederm@xmission.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=heiko.carstens@de.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=schwidefsky@de.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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