From: BitFriends <commandspider12@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Subject: Re: access guest address from within instruction
Date: Sun, 2 Oct 2022 16:52:55 +0200 [thread overview]
Message-ID: <CABVhSWPQnDCCBhCtSUFVBkyFBzPjGyvk1wixpHW0GNooQ7b32g@mail.gmail.com> (raw)
In-Reply-To: <e1538b70-8e32-a6b7-4132-77a7ea6a60fa@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2321 bytes --]
my bad, then I was mislead by "Which is, in general, what you want for
implementing a custom instruction". Also the code around me is full of gen
instructions, so I thought that's what I should use.
So, when reading the doc I found out about the cpu_{ld,st}*_mmu functions.
That sounds more what I want for a direct action, No?
Regards
BitFriends
Richard Henderson <richard.henderson@linaro.org> schrieb am So., 2. Okt.
2022, 16:40:
> On 10/2/22 02:20, BitFriends wrote:
> > I now came up with this code:
> >
> > TCGv_i64 res = 0;
> > TCGv_i64 addr = (TCGv_i64)(env->regs[R_EDI]);
> >
> > tcg_gen_qemu_ld_i64(res, addr, 0, MO_LEUQ);
> >
> > env->regs[R_EAX] = (target_ulong)res;
> >
> > However this crashes afterwards in test_bit. Maybe this is caused by an
> invalid access?
> > Anything wrong about the code? This still gives some warnings, like
> TCGv_i32 expected (and
> > when you use TCGv_i32, it says TCGv_i64 expected) plus some casting
> warnings.
>
> It is as if you did not read the second paragraph of my response at all.
> tcg_gen_qemu_ld_i64 is for generating code, not performing a direct action.
> Can you see how your code differs from *all* of the code around it?
>
> r~
>
> >
> > Am Sa., 1. Okt. 2022 um 22:23 Uhr schrieb Richard Henderson <
> richard.henderson@linaro.org
> > <mailto:richard.henderson@linaro.org>>:
> >
> > On 10/1/22 13:10, BitFriends wrote:
> > > Hello,
> > >
> > > I am trying to create a custom instruction that accesses guest
> memory specified by an
> > > address in a register. I specifically want to read from that
> address. So I tried to do
> > > that using "tcg_gen_qemu_ld_i64(&res, env->regs[R_EDI], 0,
> MO_LEUQ);", but that
> > doesn't
> > > save any result in res.
> >
> > This statement should have given you compilation errors, so I don't
> know what you mean by
> > "doesn't save any result". There's clearly a disconnect between
> what you describe and
> > what you actually attempted.
> >
> > Anyway, by the name you can see that function "gen"erates a "tcg"
> operation, which is
> > then
> > later compiled by the jit, the output of which is later executed to
> produce a result.
> > Which is, in general, what you want for implementing a custom
> instruction.
> >
> >
> > r~
> >
>
>
[-- Attachment #2: Type: text/html, Size: 3423 bytes --]
next prev parent reply other threads:[~2022-10-02 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 20:10 access guest address from within instruction BitFriends
2022-10-01 20:23 ` Richard Henderson
2022-10-01 20:59 ` BitFriends
2022-10-02 9:20 ` BitFriends
2022-10-02 14:40 ` Richard Henderson
2022-10-02 14:52 ` BitFriends [this message]
2022-10-02 17:13 ` Richard Henderson
2022-10-02 14:45 ` Peter Maydell
2022-10-02 14:57 ` BitFriends
2022-10-02 13:56 ` Alex Bennée
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=CABVhSWPQnDCCBhCtSUFVBkyFBzPjGyvk1wixpHW0GNooQ7b32g@mail.gmail.com \
--to=commandspider12@gmail.com \
--cc=qemu-devel@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).