From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13842 invoked by alias); 4 Dec 2013 18:31:58 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 13801 invoked by uid 89); 4 Dec 2013 18:31:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-ve0-f174.google.com Received: from Unknown (HELO mail-ve0-f174.google.com) (209.85.128.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 04 Dec 2013 18:30:38 +0000 Received: by mail-ve0-f174.google.com with SMTP id pa12so12581510veb.33 for ; Wed, 04 Dec 2013 10:30:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0I/solKP+eTlIkAdMiiRy/txbFzdsX21X3JYcw8U+6Q=; b=aHT2y+tTFa7G7V4RdkyFzXV0H3V9pV7wyjBHPT0DIrqevnZYFvhthlseKjKKD6LMSt 7Ezci9lgjrq0zV3Rep45Ju8uWXvEgBNtH4fGZ3L9PfMrvWe4sdXb4HTP279LZolWeBBE hNV+/s1zwVZ4fMeZbzXsKcUKq1wQD22vbdRn3tjlKd8jM6hv8o1qxNl/6xUdrUdcnLBn 6jKEgObTqn2hl4v1xP4600YDZxHUhLwZLuTclKCpkiVtipOCUAyaM7SqGsTGU89H+heY jnreeMGyjm6vt8/TuxgH4lyYu3F7+cbhCrW0OWGP6icTiAEbes/gxsYmhl9fJetLN/oE ak+Q== X-Gm-Message-State: ALoCoQmQYsa5KJ2oyhgDnoAFlTmFdya6NcD8qUuNsAh4ZQ3Lzuy0HmngXkTClTlQg/ovmFQ+CC//twcEvbL45YoGAs7y/MHxk7gUmHt7M8IAKj7Ay2Sw9lNq2PA3g6O44jHnU7tDCFFzTBzDVmxSOoiDhEVh8RBTZxd6rH1EvUWXgjzrjV8bVt/sFPwXk9JPtdG43jsnHg8MOCRynSbTMW5l/kaRbwM6+w== MIME-Version: 1.0 X-Received: by 10.220.97.145 with SMTP id l17mr1475350vcn.35.1386181830136; Wed, 04 Dec 2013 10:30:30 -0800 (PST) Received: by 10.52.163.52 with HTTP; Wed, 4 Dec 2013 10:30:30 -0800 (PST) In-Reply-To: <87ob4wr5hv.fsf@fleche.redhat.com> References: <1385735051-27558-1-git-send-email-yao@codesourcery.com> <1385735051-27558-3-git-send-email-yao@codesourcery.com> <201311291436.rATEaZ5Z030292@glazunov.sibelius.xs4all.nl> <201311291605.rATG5XVb030184@glazunov.sibelius.xs4all.nl> <52994E79.4000004@codesourcery.com> <5299B9D0.2020304@redhat.com> <529C37A2.9000207@codesourcery.com> <529E9462.9010001@codesourcery.com> <529F1B1F.2040606@redhat.com> <87ob4wr5hv.fsf@fleche.redhat.com> Date: Wed, 04 Dec 2013 18:31:00 -0000 Message-ID: Subject: Re: [PATCH 2/3] skip_prolgoue (amd64) From: Doug Evans To: Tom Tromey Cc: Pedro Alves , Yao Qi , Mark Kettenis , gdb-patches Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2013-12/txt/msg00160.txt.bz2 On Wed, Dec 4, 2013 at 7:38 AM, Tom Tromey wrote: >>>>>> "Pedro" == Pedro Alves writes: > > Pedro> Actually "non-stop", vs "all-stop" here isn't the ideal > Pedro> predicate. The real predicate is "is any thread running". > Pedro> "non-stop" is just being currently used in > Pedro> prepare_execute_command as proxy for that, just because > Pedro> that was the easiest. > > It seemed to me that the predicate must be "is any thread associated > with this particular address space running?" -- but I wanted to ask if > that makes sense, or if that was what you meant. This idea seems to > open the door to finer-grained cache flushing. It would be unfortunate to take an unnecessary perf hit when doing a backtrace and then browsing the stack, or setting a breakpoint in non-stop mode when, for example, I'm stopped in some thread for whatever reason (and then other threads happen to have their own events). I think some kind of finer-grained flushing *could* be reasonable. Implementing it may then make the cache "look like" it is a stack cache and code cache. 1/2 :-) [One could do something like record in each line an attribute describing how/where it came from.]