From: Stefan Hajnoczi <stefanha@gmail.com>
To: ali saeedi <ali.saeedi56@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] BIT_WORD(start >> TARGET_PAGE_BITS)
Date: Fri, 30 Jun 2017 14:53:52 +0100 [thread overview]
Message-ID: <CAJSP0QUKJdeTcupGBkdj_kLS-J-LW24ym9Z-dcWf1rxWZyk6cw@mail.gmail.com> (raw)
In-Reply-To: <CAGKXQyct2Y0DTbSRxCjyDJpR0eSZg3L245mce6QvmtPNJexcrw@mail.gmail.com>
On Fri, Jun 30, 2017 at 2:02 PM, ali saeedi <ali.saeedi56@gmail.com> wrote:
> Hello
> what does the following code do?
> 'unsigned long page = BIT_WORD(start >> TARGET_PAGE_BITS)' ?
> thanks a lot
Aside from Eric's response, I want to mention that I've noticed your
frequent questions too.
A volunteer project like QEMU can only make progress if people "give"
more than they "take".
Each question you ask takes someone's time. Often the person
responding searches the code base for you and then replies with the
answer.
If you keep demanding time and attention without giving back to QEMU
then people notice this and they will stop responding.
I'm not trying to attack you, just letting you know what I've often
seen happen when someone wants more support than the volunteers are
willing to give.
This is an opportunity to do two things:
1. Learn to answer your own questions by reading the code, adding
printfs, using a debugger, and other techniques. This will make you
more independent and you'll be more productive.
2. Start contributing to QEMU by reviewing patches on the mailing
list, helping users on #qemu IRC, etc.
I'd be happy to discuss how to do these things in more detail.
Stefan
prev parent reply other threads:[~2017-06-30 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:02 [Qemu-devel] BIT_WORD(start >> TARGET_PAGE_BITS) ali saeedi
2017-06-30 13:19 ` Eric Blake
2017-06-30 13:49 ` ali saeedi
2017-06-30 13:53 ` Stefan Hajnoczi [this message]
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=CAJSP0QUKJdeTcupGBkdj_kLS-J-LW24ym9Z-dcWf1rxWZyk6cw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=ali.saeedi56@gmail.com \
--cc=qemu-devel@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: 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).