From: Jason Baron <jbaron@redhat.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, avi@redhat.com,
Roland McGrath <roland@hack.frob.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] core dump: drop VM_ALWAYSDUMP flag
Date: Wed, 7 Mar 2012 16:36:37 -0500 [thread overview]
Message-ID: <20120307213637.GC2409@redhat.com> (raw)
In-Reply-To: <4F57D296.8090608@tilera.com>
On Wed, Mar 07, 2012 at 04:26:46PM -0500, Chris Metcalf wrote:
> On 3/7/2012 4:19 PM, Jason Baron wrote:
> > On Wed, Mar 07, 2012 at 11:43:02AM -0800, Roland McGrath wrote:
> >>> well, sure, we can provide an arch interface, for this check. I'm more
> >>> concerned with the general idea. If it seems ok, I can re-do this bit
> >>> with an arch interface.
> >> Anything based on strcmp is dismal. VM_ALWAYSDUMP was nice and clean.
> >> A hook along the lines of arch_vma_name would be clean enough I suppose.
> >> In fact, there is only one instance today (tile) where arch_vma_name()!=NULL
> >> wouldn't do just what you need.
> >>
> > Yeah, so I think something like the following would work (adding Tile
> > maintainer to 'cc list).
>
> Thanks!
>
> My instinct would be not to special-case it in always_dump_vma(). Since
> it's just a one-page region anyway, and it is at least potentially
> interesting, I'm happy to always dump it. Alternately, we can just get rid
> of the "[intrpt]" name, which I just put in to be cute (and since it was
> easy to identify the mapping in question). Regardless, since that region
> doesn't exist on our current 64-bit architecture, I'm not too concerned
> with how it's handled going forward, since I expect the 32-bit platform to
> become less popular over time. I'd vote for generic code cleanliness.
>
Ok, I'll just always dump it.
Thanks!
-Jason
next prev parent reply other threads:[~2012-03-07 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 17:00 [Qemu-devel] [PATCH 0/2] core dump: re-purpose VM_ALWAYSDUMP to user controlled VM_DONTDUMP Jason Baron
2012-03-07 17:00 ` [Qemu-devel] [PATCH 1/2] core dump: drop VM_ALWAYSDUMP flag Jason Baron
2012-03-07 17:59 ` Roland McGrath
2012-03-07 18:50 ` Jason Baron
2012-03-07 19:43 ` Roland McGrath
2012-03-07 21:19 ` Jason Baron
2012-03-07 21:26 ` Chris Metcalf
2012-03-07 21:36 ` Jason Baron [this message]
2012-03-07 21:41 ` Roland McGrath
2012-03-07 17:00 ` [Qemu-devel] [PATCH 2/2] core dump: add a new VM_DONTDUMP flag Jason Baron
2012-03-07 22:30 ` [Qemu-devel] [PATCH 0/2] core dump: re-purpose VM_ALWAYSDUMP to user controlled VM_DONTDUMP Andrew Morton
2012-03-08 1:32 ` Jason Baron
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=20120307213637.GC2409@redhat.com \
--to=jbaron@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=roland@hack.frob.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;
as well as URLs for NNTP newsgroup(s).