From: Alistair Francis <alistair23@gmail.com> To: Bin Meng <bmeng.cn@gmail.com> Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>, Palmer Dabbelt <palmer@dabbelt.com>, Alistair Francis <alistair.francis@wdc.com>, "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org> Subject: Re: [PATCH v1 1/1] riscv: Pass RISCVHartArrayState by pointer Date: Sat, 16 Jan 2021 09:50:42 -0800 [thread overview] Message-ID: <CAKmqyKNV0v9RJ_57UrD9Xsnexh9SMh47VZ2Zsp0xQXN0i9-3sg@mail.gmail.com> (raw) In-Reply-To: <CAEUhbmWC5CDqK3QuuLY9PFAxr=OcePsJqsUQjhw3em5GOH+Ccg@mail.gmail.com> On Sat, Jan 16, 2021 at 8:30 AM Bin Meng <bmeng.cn@gmail.com> wrote: > > On Sat, Jan 16, 2021 at 7:00 AM Alistair Francis > <alistair.francis@wdc.com> wrote: > > > > We were accidently passing RISCVHartArrayState by value instead of > > pointer. The type is 824 bytes long so let's correct that and pass it by > > pointer instead. > > > > Fixes: Coverity CID 1438099 > > Fixes: Coverity CID 1438100 > > Fixes: Coverity CID 1438101 > > Where can I look at the Coverity report for QEMU? I don't think you can. I think there are only a few people who can see them and they just report them to everyone else. > > > Signed-off-by: Alistair Francis <alistair.francis@wdc.com> > > --- > > include/hw/riscv/boot.h | 6 +++--- > > hw/riscv/boot.c | 8 ++++---- > > hw/riscv/sifive_u.c | 10 +++++----- > > hw/riscv/spike.c | 8 ++++---- > > hw/riscv/virt.c | 8 ++++---- > > 5 files changed, 20 insertions(+), 20 deletions(-) > > > > Reviewed-by: Bin Meng <bin.meng@windriver.com> Thanks! Alistair
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Francis <alistair23@gmail.com> To: Bin Meng <bmeng.cn@gmail.com> Cc: Alistair Francis <alistair.francis@wdc.com>, "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>, "open list:RISC-V" <qemu-riscv@nongnu.org>, Palmer Dabbelt <palmer@dabbelt.com> Subject: Re: [PATCH v1 1/1] riscv: Pass RISCVHartArrayState by pointer Date: Sat, 16 Jan 2021 09:50:42 -0800 [thread overview] Message-ID: <CAKmqyKNV0v9RJ_57UrD9Xsnexh9SMh47VZ2Zsp0xQXN0i9-3sg@mail.gmail.com> (raw) In-Reply-To: <CAEUhbmWC5CDqK3QuuLY9PFAxr=OcePsJqsUQjhw3em5GOH+Ccg@mail.gmail.com> On Sat, Jan 16, 2021 at 8:30 AM Bin Meng <bmeng.cn@gmail.com> wrote: > > On Sat, Jan 16, 2021 at 7:00 AM Alistair Francis > <alistair.francis@wdc.com> wrote: > > > > We were accidently passing RISCVHartArrayState by value instead of > > pointer. The type is 824 bytes long so let's correct that and pass it by > > pointer instead. > > > > Fixes: Coverity CID 1438099 > > Fixes: Coverity CID 1438100 > > Fixes: Coverity CID 1438101 > > Where can I look at the Coverity report for QEMU? I don't think you can. I think there are only a few people who can see them and they just report them to everyone else. > > > Signed-off-by: Alistair Francis <alistair.francis@wdc.com> > > --- > > include/hw/riscv/boot.h | 6 +++--- > > hw/riscv/boot.c | 8 ++++---- > > hw/riscv/sifive_u.c | 10 +++++----- > > hw/riscv/spike.c | 8 ++++---- > > hw/riscv/virt.c | 8 ++++---- > > 5 files changed, 20 insertions(+), 20 deletions(-) > > > > Reviewed-by: Bin Meng <bin.meng@windriver.com> Thanks! Alistair
next prev parent reply other threads:[~2021-01-16 17:52 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-15 23:00 [PATCH v1 1/1] riscv: Pass RISCVHartArrayState by pointer Alistair Francis 2021-01-15 23:00 ` Alistair Francis 2021-01-15 23:03 ` Palmer Dabbelt 2021-01-15 23:03 ` Palmer Dabbelt 2021-01-16 16:30 ` Bin Meng 2021-01-16 16:30 ` Bin Meng 2021-01-16 17:50 ` Alistair Francis [this message] 2021-01-16 17:50 ` Alistair Francis 2021-01-16 18:55 ` Alistair Francis 2021-01-16 18:55 ` Alistair Francis 2021-01-16 22:32 ` Philippe Mathieu-Daudé 2021-01-16 22:32 ` Philippe Mathieu-Daudé 2021-01-16 22:38 ` Alistair Francis 2021-01-16 22:38 ` Alistair Francis 2021-01-17 16:52 ` Philippe Mathieu-Daudé 2021-01-17 16:52 ` Philippe Mathieu-Daudé 2021-01-19 21:50 ` Eric Blake 2021-01-19 21:50 ` Eric Blake 2021-01-18 17:14 ` Richard Henderson 2021-01-18 17:14 ` Richard Henderson
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=CAKmqyKNV0v9RJ_57UrD9Xsnexh9SMh47VZ2Zsp0xQXN0i9-3sg@mail.gmail.com \ --to=alistair23@gmail.com \ --cc=alistair.francis@wdc.com \ --cc=bmeng.cn@gmail.com \ --cc=palmer@dabbelt.com \ --cc=qemu-devel@nongnu.org \ --cc=qemu-riscv@nongnu.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.