public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Gerlicher, Klaus" <klaus.gerlicher@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "'Saiapova, Natalia'" <natalia.saiapova@intel.com>
Subject: [PING][PATCH v2 0/6] Refinement of scheduler-locking settings
Date: Tue, 20 Aug 2024 14:42:14 +0000	[thread overview]
Message-ID: <SN7PR11MB7091507A21D493AE5E17E055E88D2@SN7PR11MB7091.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5632ED98E31E9AFBBF72A9648DA62@SJ0PR11MB5632.namprd11.prod.outlook.com>

Hi all,

I've inherited this from Natalia (all the best to you, Natalia) and I wonder if we could get a review here since I haven't seen any activity.

Thank
Klaus

> -----Original Message-----
> From: Saiapova, Natalia <natalia.saiapova@intel.com>
> Sent: Friday, July 12, 2024 1:13 PM
> To: gdb-patches@sourceware.org
> Cc: Gerlicher, Klaus <klaus.gerlicher@intel.com>
> Subject: RE: [PATCH v2 0/6] Refinement of scheduler-locking settings
> 
> Hi all,
> 
> Unfortunately, I won't be able to keep track on this patch series myself, but
> Klaus has kindly agreed to follow it up.
> 
> Regards
> Natalia
> 
> > -----Original Message-----
> > From: Natalia Saiapova <natalia.saiapova@intel.com>
> > Sent: Tuesday, July 9, 2024 5:04 PM
> > To: gdb-patches@sourceware.org
> > Subject: [PATCH v2 0/6] Refinement of scheduler-locking settings
> >
> > Hi all,
> >
> > Here is the version 2 of the scheduler locking refinement patches.
> > I rebased and updated them based on Tom's and Eli's feedback.
> >
> > The main difference with v1 is that there is an intermediate step of
> > the refinement where I introduce the "non-step" option for all non-stepping
> > commands, which then gets replaced with "eval" for function calls and
> > "continue" for continuing commands.  Also, I renamed "run" to "continue"
> > to match the following manual page:
> > https://sourceware.org/gdb/current/onlinedocs/gdb.html/Continuing-and-
> > Stepping.html
> >
> > Regards,
> > Natalia
> >
> > Natalia Saiapova (6):
> >   gdb: use schedlock_applies in user_visible_resume_ptid.
> >   gdb, cli: remove left-over code from "set_logging_on".
> >   gdb, cli: pass the argument of a set command to its callback.
> >   gdb: change the internal representation of scheduler locking.
> >   gdb: refine commands to control scheduler locking.
> >   gdb: add eval option to lock the scheduler during infcalls.
> >
> >  gdb/NEWS                                      |  25 ++
> >  gdb/cli/cli-logging.c                         |   5 -
> >  gdb/cli/cli-setshow.c                         |   2 +-
> >  gdb/doc/gdb.texinfo                           |  82 +++-
> >  gdb/infrun.c                                  | 401 +++++++++++++++---
> >  .../gdb.mi/user-selected-context-sync.exp     |  23 +-
> >  .../gdb.threads/hand-call-in-threads.exp      |  12 +-
> >  .../multiple-successive-infcall.exp           |   7 +-
> >  gdb/testsuite/gdb.threads/schedlock.exp       | 105 ++++-
> >  gdb/testsuite/lib/gdb.exp                     |  71 +++-
> >  10 files changed, 611 insertions(+), 122 deletions(-)
> >
> > --
> > 2.25.1
> >
> > Intel Deutschland GmbH
> > Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> > Tel: +49 89 99 8853-0, www.intel.de
> > Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
> > Chairperson of the Supervisory Board: Nicole Lau
> > Registered Office: Munich
> > Commercial Register: Amtsgericht Muenchen HRB 186928

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2024-08-20 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 15:04 [PATCH " Natalia Saiapova
2024-07-09 15:04 ` [PATCH v2 1/6] gdb: use schedlock_applies in user_visible_resume_ptid Natalia Saiapova
2024-07-09 15:04 ` [PATCH v2 2/6] gdb, cli: remove left-over code from "set_logging_on" Natalia Saiapova
2024-07-09 15:04 ` [PATCH v2 3/6] gdb, cli: pass the argument of a set command to its callback Natalia Saiapova
2024-07-09 15:04 ` [PATCH v2 4/6] gdb: change the internal representation of scheduler locking Natalia Saiapova
2024-07-09 15:04 ` [PATCH v2 5/6] gdb: refine commands to control " Natalia Saiapova
2024-07-09 15:57   ` Eli Zaretskii
2024-07-09 15:04 ` [PATCH v2 6/6] gdb: add eval option to lock the scheduler during infcalls Natalia Saiapova
2024-07-09 16:00   ` Eli Zaretskii
2024-07-12 11:13 ` [PATCH v2 0/6] Refinement of scheduler-locking settings Saiapova, Natalia
2024-08-20 14:42   ` Gerlicher, Klaus [this message]
2024-09-10 14:43     ` [PING V2][PATCH " Gerlicher, Klaus
2024-10-02 14:14       ` [PING V3][PATCH " Gerlicher, Klaus
2024-10-22 11:59         ` [PING V4][PATCH " Gerlicher, Klaus

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=SN7PR11MB7091507A21D493AE5E17E055E88D2@SN7PR11MB7091.namprd11.prod.outlook.com \
    --to=klaus.gerlicher@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=natalia.saiapova@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).