qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target/xtensa: drop num_[core_]regs from dc232b/dc233c configs
Date: Mon, 12 Nov 2018 00:52:53 +0100	[thread overview]
Message-ID: <CAAdtpL4r52iMNzUtKEDvdwOVomGEfL9paPNGMyj=VG23sFQOSw@mail.gmail.com> (raw)
In-Reply-To: <13f47aff-593a-e35e-959b-4ddd9f6c6121@linaro.org>

Hi Max,

On Thu, Nov 1, 2018 at 12:02 AM Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> On 10/31/18 9:35 PM, Max Filippov wrote:
> > gdb_regmap::num_core_regs field is initialized incorrectly in the dc232b
> > and dc233c configurations. As a result the following message is
> > displayed when attaching to an xtensa linux-user process:
> >
> >   "Register 105 is not available",
> >
> > and gdb is unable to control the inferior.
> >
> > Now that xtensa_count_regs does the right thing, remove manual
> > initialization of these fields from the affected configurations and let
> > xtensa_finalize_config initialize them.
> >
> > Cc: qemu-stable@nongnu.org
> > Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> > ---
> >  target/xtensa/core-dc232b.c | 2 --
> >  target/xtensa/core-dc233c.c | 2 --
> >  2 files changed, 4 deletions(-)
>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

Can we include this patch for the 3.2 release?

Thanks,

Phil.

  reply	other threads:[~2018-11-11 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 21:35 [Qemu-devel] [PATCH] target/xtensa: drop num_[core_]regs from dc232b/dc233c configs Max Filippov
2018-10-31 23:00 ` Richard Henderson
2018-11-11 23:52   ` Philippe Mathieu-Daudé [this message]
2018-11-12  2:17     ` Max Filippov

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='CAAdtpL4r52iMNzUtKEDvdwOVomGEfL9paPNGMyj=VG23sFQOSw@mail.gmail.com' \
    --to=f4bug@amsat.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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).