From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Chris Metcalf <cmetcalf@ezchip.com>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] linux-user/syscall.c: Fix typo issue for using target_vec[i].iov_len instead of target_vec[i].iov_base
Date: Fri, 23 Jan 2015 18:57:28 +0800 [thread overview]
Message-ID: <54C22918.8040505@sunrus.com.cn> (raw)
In-Reply-To: <CAFEAcA_NG4E5tc8nQ8EbVDqs=704cnXJZerVAVg-c74VQm5c+Q@mail.gmail.com>
Thank you for all of your work.
I plan to let qemu support tile architecture: "can let gcc run testsuite
with qemu for tile". It is really hard to me, but I should try, it is my
duty (I met it, and it's within my boarder, although no one pay for me).
:-)
At present, I am just preparing:
- Reading architecture related documents (thank tile kernel member, who
let me know about all tile architecture related documents).
- Reading qemu architecture related code for understanding how to add
tile code for qemu.
- After preparing, I should provide a schedule for it (the steps, and
the time point, and the risks which I may face to). Hope I can finish
preparing within this month.
Welcome any ideas, suggestions and completions by any members, e.g.
- Share any related documents or knowledge for architecture.
- Is there any original code for tile? Maybe originally, someone tried
qemu for tile, but the related code was not merged into main line.
- Suggestions about the schedule: the common steps, the time resources
may need, and which risks have to face to.
Thanks.
On 1/23/15 18:08, Peter Maydell wrote:
> On 23 January 2015 at 10:07, Chen Gang S <gang.chen@sunrus.com.cn> wrote:
>> It is only a typo issue, need use tswapal(target_vec[i].iov_len) for the
>> len.
>>
>> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
>> ---
>> linux-user/syscall.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>> index a66c2ae..8260ed7 100644
>> --- a/linux-user/syscall.c
>> +++ b/linux-user/syscall.c
>> @@ -1896,7 +1896,7 @@ static void unlock_iovec(struct iovec *vec, abi_ulong target_addr,
>> if (target_vec) {
>> for (i = 0; i < count; i++) {
>> abi_ulong base = tswapal(target_vec[i].iov_base);
>> - abi_long len = tswapal(target_vec[i].iov_base);
>> + abi_long len = tswapal(target_vec[i].iov_len);
>> if (len < 0) {
>> break;
>> }
>> --
>> 1.9.3 (Apple Git-50)
>
> Nice catch.
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> thanks
> -- PMM
>
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-01-23 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 10:07 [Qemu-devel] [PATCH] linux-user/syscall.c: Fix typo issue for using target_vec[i].iov_len instead of target_vec[i].iov_base Chen Gang S
2015-01-23 10:08 ` Peter Maydell
2015-01-23 10:57 ` Chen Gang S [this message]
2015-01-23 11:21 ` Peter Maydell
2015-01-23 14:01 ` Chen Gang S
2015-01-23 13:55 ` Peter Maydell
2015-01-23 21:10 ` Chen Gang S
2015-01-27 15:39 ` Michael Tokarev
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=54C22918.8040505@sunrus.com.cn \
--to=gang.chen@sunrus.com.cn \
--cc=cmetcalf@ezchip.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).